Method and system for co-browsing in a B2C architecture through co-browsing functionality embedded in content of a content provider as initiated by a guest to a co-browse session

ABSTRACT

A method includes establishing a first communication session between a first web browser associated with a user and a content provider over a network to deliver content including embedded co-browsing functionality. A second communication session is established between a second device and a co-browse communication server to initiate a co-browse session having a session identifier, wherein the second device is a guest. A user identifier and the session identifier is delivered from the second device to the content provider. The co-browsing functionality is exposed with an icon, such that when the icon is activated at the first device, the first web browser is joined into the co-browse session. The co-browse session is established between the first web browser as a host and a second web browser, such that content at the first web browser is delivered to the second web browser via the co-browse communication server through the co-browse session.

CROSS REFERENCE TO RELATED APPLICATIONS

This present application claims priority to and the benefit of thecommonly owned, provisional patent application, U.S. Ser. No.61/872,630, entitled “METHOD AND SYSTEM FOR CO-BROWSING,” with filingdate Aug. 30, 2013, which is herein incorporated by reference in itsentirety.

BACKGROUND

Co-browsing allows at least two participating parties to viewsubstantially the same content that is deliverable through a network.For example, co-browsing provides a way for two participants to have apersonal shopping experience while online, such that it simulates theexperience of physical shopping. The two participants may also have aseparate phone connection that allows both to comment on products viewedthrough the co-browsing session.

In the past, a proxy server acts as an intermediary source of webcontent deliverable to both participants in the co-browsing session. Forexample, the proxy server receives content from a web site, and thenforwards the content to each of the participants in the co-browsingsession. Because the content is sourced at the proxy server, the proxyserver is able to deliver the same content to each of the participants.

One of the issues with having a proxy server as an intermediate sourceof content is that if there are problems at the proxy server, then bothconnections to the participants will suffer. For example, if theconnection between the content provider and the proxy server goes down,then both participants will also cease receiving data. In anotherexample, if the proxy server is experiencing difficulties in processingthe content and formatting it for delivering the co-browsing session,then both participants will also experience those difficulties, such as,delays in inputting and/or receiving information, poor response times,poor quality of multimedia (e.g., data, video, audio), and more. Thesedifficulties experienced at the proxy server will be experienced by theparticipants.

What is needed is a co-browsing architecture that allows for aco-browsing experience that is seamless with an original browsingsession.

SUMMARY

A method for co-browsing, such as, between a business and a customer, inone embodiment. The method includes establishing a first communicationsession between a first web browser of first device (e.g., of thecustomer) and a content provider (e.g., business) over a network todeliver content to the first web browser from the content provider. Thefirst device is associated with a first user. In addition, the contentincludes embedded co-browsing functionality that allows for co-browsingbetween two or more parties. The method includes establishing a secondcommunication session between a second device (e.g., agent of thebusiness) and a co-browse communication server to initiate a co-browsesession, wherein the co-browse session comprises a co-browse sessionidentifier, and wherein the second device acts as a guest in theco-browse session. The method includes sending a user identifierassociated with the first user and the co-browse session identifier fromthe second device to the content provider. The method includes exposingthe co-browsing functionality in the content delivered to the first webbrowser with an icon comprising the co-browse session identifier, suchthat when the icon is activated at the first device, the first webbrowser is joined into the co-browse session. The method includesestablishing the co-browse session between the first web browser of thefirst device as a host and a second web browser of the second device,such that the content at the first web browser is delivered to thesecond web browser of the second device via the co-browse communicationserver through the co-browse session

A system for co-browsing, such as, between a business and a customer, isdescribed in another embodiment. The system includes a first deviceincluding a first web browser for communicating over a network, whereinthe first device is associated with a first user. A content providerprovides content, wherein the content includes embedded co-browsingfunctionality that allows for co-browsing between two or more parties. Afirst communication session between the first web browser of the firstdevice and the content provider over the network delivers content to thefirst web browser from the content provider. A second device including asecond web browser communicates over the network. A co-browsecommunication server provides a co-browse session comprising a co-browsesession identifier. A second communication session between the seconddevice and the co-browse communication server initiates the co-browsesession, wherein the second device acts as a guest in the co-browsesession. A third communication session between the second device and thecontent provider delivers the user identifier and the co-browse sessionidentifier to the content provider. The co-browsing functionality in thecontent delivered to the first web browser is exposed with an iconcomprising the co-browse session identifier, such that when the icon isactivated at the first device, the first web browser is joined into theco-browse session. The co-browse session is established between thefirst web browser of the first device as a host and a second web browserof the second device, such that the content at the first web browser isdelivered to the second web browser of the second device via theco-browse communication server through the co-browse session

A method for co-browsing, such as between two customers of a business,in one embodiment. The method includes establishing a firstcommunication session between a first web browser of first device (e.g.,of a first customer) and a content provider over a network to delivercontent to the first web browser from the content provider, wherein thecontent comprises embedded co-browsing functionality allowingco-browsing between two or more parties. The method includes receiving arequest for activating the co-browsing functionality at the firstdevice. The method includes establishing a second communication sessionbetween the first web browser and a co-browse communication server toinitiate a co-browse session, wherein the co-browse session comprises aco-browse session identifier, wherein the first device acts as a host inthe co-browse session. The method includes establishing a thirdcommunication session between a second web browser of a second device(e.g., a second customer) and the co-browse communication server to jointhe second web browser into the co-browse session based on the co-browsesession identifier. The method includes establishing the co-browsesession between the first web browser as the host and the second webbrowser of the second device as a guest, such that the content at thefirst web browser is delivered to the second web browser via theco-browse communication sever over the co-browse session.

A system for co-browsing, such as between two customers of a business,in one embodiment. The system includes a first device comprising a firstweb browser for communicating over a network. A content providerprovides content including embedded co-browsing functionality allowingco-browsing between two or more parties. A first communication sessionbetween the first web browser and the content provider over the networkdelivers the content to the first web browser from the content provider.A second device including a second web browser communicates over thenetwork. A co-browse communication server provides a co-browse sessionincluding a co-browse session identifier. A second communication sessionestablished between the first web browser and the co-browsecommunication server initiates the co-browse session including aco-browse session identifier, wherein the second communication sessionis established in response to receiving a request for activating theco-browse functionality at the first device, wherein the first deviceacts as a host in the co-browse session. A third communication sessionestablished between the second web browser and the co-browsecommunication server joins the second web browser into the co-browsesession based on the co-browse session identifier. Wherein the co-browsesession is established between the first web browser as the host and thesecond web browser of the second device as a guest, such that thecontent at the first web browser is delivered to the second web browservia the co-browse communication sever over the co-browse session.

A method for co-browsing between multiple parties is described inembodiments. The method includes establishing a first communicationsession between a first web browser of first device and a first contentprovider over a network to deliver content to the first web browser fromthe first content provider. The method includes accessing a co-browseextension on the first web browser to enable multi-domain co-browsingfunctionality on the first web browser. The method includes establishinga second communication session between the first web browser and aco-browse communication server to initiate and join the first webbrowser in a co-browse session, wherein the co-browse session comprisesa co-browse session identifier, wherein the first device acts as a hostin the co-browse session. The method includes establishing a thirdcommunication session between a second web browser of a second deviceand the co-browse communication server to join the second web browserinto the co-browse session, such that content at the first web browseris delivered to the second web browser of the second device via theco-browse communication server.

A system for co-browsing between multiple parties is described inembodiments. The system includes a first communication sessionestablished between a first web browser of first device and a firstcontent provider over a network to deliver content to the first webbrowser from the first content provider. A co-browse extensionaccessible on the first web browser that enables multi-domainco-browsing functionality on the first web browser. A secondcommunication session established between the first web browser and aco-browse communication server initiates and joins the first web browserin a co-browse session, wherein the co-browse session includes aco-browse session identifier, wherein the first device acts as a host inthe co-browse session. A third communication session between a secondweb browser of a second device and the co-browse communication serverjoins the second web browser into the co-browse session, such thatcontent at the first web browser is delivered to the second web browserof the second device via the co-browse communication server.

A method is described for inviting a guest into a co-browse session,wherein the guest is logged into a network. In particular, on the hostside, within the browser, a small extension is installed to enableco-browsing via the communication server facilitating co-browsing, andinvite one or more guests that are logged into a network. The log-in maybe on any supported and verifiable website, such as, a third partysocial network, or an insurance company network, or even thewebsite/service that provides co-browsing services. For example, boththe host and the guest are logged into the network supporting theco-browsing, and as such, both are identified to each other. In the caseof a guest that is logged into a third party social networking site, thehost is able to select a friend, invite that friend through the thirdparty social network communications platform (e.g., Facebook message onthat friend's wall), and establish a co-browsing session upon acceptanceof the invite. More particularly, the extension provides for the displayof a small co-browsing widget, for example. In order to commenceco-browsing, the host first logs into the system. The host then enters aguest identification field. Since the guest is logged in, anidentification of the guest can be found using the guest's log-ininformation. Once selected, a small message with session number isdisplayed on the guest's computer display (e.g., through a messagingboard) and through the network upon which the guest is logged-in. Whenthe session number is selected, the co-browsing session is established.

A method for establishing a co-browse session is described, wherein theguest is not logged into any site identifiable by the co-browse session,in accordance with one embodiment of the present disclosure. On the hostside, within the browser, a small extension is installed to enableco-browsing via the co-browse communication server facilitating theco-browsing session, as previously described. In another implementation,the functionality is provided at the .com website, as previouslydescribed. This extension provides for the display of a smallco-browsing widget. In order to commence co-browsing, the user or hostfirst logs into the system. To invite another user to join, the hostthen enters information into a guest identification field selectablethrough interface 1030. The user can enter a guest identification and acommunication method (e.g., email, token, etc.) to the guest. In oneexample, the guest is identified via an email address. The email addressis used to send the guest an email which contains a session key. Uponthe guest selecting the session key, a co-browsing session is startedbetween the host and guest. The guest need not have the extensioninstalled on the guest browser. Aside from email, the guest can becontacted via other communication methods, e.g., on-line chat, phone,etc. In addition, no native application need be installed on the guestcomputer.

In another embodiment, a method for co-browsing in a mobile environmentis described. The method includes providing a mobile applicationexecutable on a mobile device, wherein the mobile application comprisesa co-browsing functionality; and wrapping browser functionality with themobile application, such that web browsing is enabled when executing theco-browsing functionality. For example, the browser functionality may beaccessed within a library of functionalities, such that the methodincludes providing a library of functionalities comprising a firstfunctionality enabling browser functionality; and calling the firstfunctionality within the mobile application.

In still another embodiment, a method for displaying multiple pointersin a co-browsing environment is described. The method includesestablishing a co-browse session between a host device and one or moreguest devices. The method includes displaying a local pointer on a localdevice. The method includes displaying a remote pointer on the localdevice, wherein the remote pointer is associated with a device remotefrom the local device, and includes one or more features distinguishingthe remote pointer from the local pointer.

In another embodiment, a method of co-browsing is described. The methodincludes providing a first user interface viewable on a display of adevice. The method includes providing one or more widgets providingco-browsing functionalities. For instance, the method includes providinga widget in the user interface on a host device enabling an initiationof a co-browse session between a host and at least one guest.

In still another embodiment, a method of co-browsing is described,wherein the method includes establishing a co-browse session between ahost device and one or more guest devices. The method includes accessinga first page from a first web site on the co-browse session. The methodincludes capturing a first snapshot of the first page. The methodincludes storing the first snapshot in a repository associated with auser of the host device.

These and other objects and advantages of the various embodiments of thepresent disclosure will be recognized by those of ordinary skill in theart after reading the following detailed description of the embodimentsthat are illustrated in the various drawing figures.

BRIEF DESCRIPTION

The accompanying drawings, which are incorporated in and form a part ofthis specification and in which like numerals depict like elements,illustrate embodiments of the present disclosure and, together with thedescription, serve to explain the principles of the disclosure.

FIG. 1 depicts a block diagram of an exemplary computer system suitablefor implementing the present methods, in accordance with one embodimentof the present disclosure.

FIG. 2 is an illustration of an information flow diagram showing theflow of information through a co-browse system that is capable ofestablishing a co-browse session between two parties (e.g., a customerand an agent of a business) through co-browsing functionality embeddedin content provided by a content provider, in accordance with oneembodiment of the present disclosure.

FIG. 3A is a flow diagram illustrating steps in a method for providingco-browsing between two parties through co-browsing functionalityembedded in content provided by a content provider, in accordance withone embodiment of the present disclosure.

FIG. 3B is a flow diagram illustrating steps in a method for providingco-browsing between two parties by a participating content provider, andmore specifically though co-browsing functionality embedded in contentprovided by the content provider, in accordance with one embodiment ofthe present disclosure.

FIG. 4 is an illustration of an information flow diagram showing theflow of information through a co-browse system that is capable ofestablishing a co-browse session between two parties (e.g., two or moreconsumers) through co-browsing functionality embedded in contentprovided by a content provider, in accordance with one embodiment of thepresent disclosure.

FIG. 5 is a flow diagram illustrating steps in a method for providingco-browsing between two or more parties through co-browsingfunctionality embedded in content provided by a content provider, inaccordance with one embodiment of the present disclosure.

FIG. 6 is an illustration of an information flow diagram showing theflow of information through a co-browse system that is capable ofestablishing a co-browse session between two or more parties of multipledomains (e.g., web sites) through a co-browsing extension to a webbrowser, in accordance with one embodiment of the present disclosure.

FIG. 7 is a flow diagram illustrating steps in a method for establishinga co-browse session between two or more parties of multiple domains(e.g., web sites) through a co-browsing extension to a web browser, inaccordance with one embodiment of the present disclosure.

FIG. 8 is an illustration of the implementation of co-browsing through amobile application, in accordance with one embodiment of the invention.

FIG. 9 is an illustration of a plurality of pointers in a co-browsesession, each of which is distinct and unique from the other pointersfor immediate identification, in accordance with one embodiment of theinvention.

FIG. 10 are illustrations of a co-browse widget that is layered over orwithin the content provided by a co-browsing session at displays for ahost and a guest, wherein each corresponding widget provides controlover the co-browse session, in accordance with one embodiment of theinvention.

FIG. 11 is an illustration of a history of links or websites visitedruing a particular co-browse session, in accordance with one embodimentof the invention.

DETAILED DESCRIPTION

Reference will now be made in detail to the various embodiments of thepresent disclosure, examples of which are illustrated in theaccompanying drawings. While described in conjunction with theseembodiments, it will be understood that they are not intended to limitthe disclosure to these embodiments. On the contrary, the disclosure isintended to cover alternatives, modifications and equivalents, which maybe included within the spirit and scope of the disclosure as defined bythe appended claims. Furthermore, in the following detailed descriptionof the present disclosure, numerous specific details are set forth inorder to provide a thorough understanding of the present disclosure.However, it will be understood that the present disclosure may bepracticed without these specific details. In other instances, well-knownmethods, procedures, components, and circuits have not been described indetail so as not to unnecessarily obscure aspects of the presentdisclosure.

Some portions of the detailed descriptions that follow are presented interms of procedures, logic blocks, processing, and other symbolicrepresentations of operations on data bits within a computer memory.These descriptions and representations are the means used by thoseskilled in the data processing arts to most effectively convey thesubstance of their work to others skilled in the art. In the presentapplication, a procedure, logic block, process, or the like, isconceived to be a self-consistent sequence of steps or instructionsleading to a desired result. The steps are those utilizing physicalmanipulations of physical quantities. Usually, although not necessarily,these quantities take the form of electrical or magnetic signals capableof being stored, transferred, combined, compared, and otherwisemanipulated in a computer system. It has proven convenient at times,principally for reasons of common usage, to refer to these signals astransactions, bits, values, elements, symbols, characters, samples,pixels, or the like.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise as apparent from the followingdiscussions, it is appreciated that throughout the present disclosure,discussions utilizing terms such as “browsing,” “co-browsing,” or thelike, refer to actions and processes of a computer system or similarelectronic computing device or processor (e.g., system 100). Thecomputer system or similar electronic computing device manipulates andtransforms data represented as physical (electronic) quantities withinthe computer system memories, registers or other such informationstorage, transmission or display devices.

Other embodiments described herein may be discussed in the generalcontext of computer-executable instructions residing on some form ofcomputer-readable storage medium, such as program modules, executed byone or more computers or other devices. By way of example, and notlimitation, computer-readable storage media may comprise non-transitorycomputer storage media and communication media. Generally, programmodules include routines, programs, objects, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. The functionality of the program modules may becombined or distributed as desired in various embodiments.

Computer storage media includes volatile and nonvolatile, removable andnon-removable media implemented in any method or technology for storageof information such as computer-readable instructions, data structures,program modules or other data. Computer storage media includes, but isnot limited to, random access memory (RAM), read only memory (ROM),electrically erasable programmable ROM (EEPROM), flash memory or othermemory technology, compact disk ROM (CD-ROM), digital versatile disks(DVDs) or other optical storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any othermedium that can be used to store the desired information and that canaccessed to retrieve that information.

Communication media can embody computer-executable instructions, datastructures, and program modules, and includes any information deliverymedia. By way of example, and not limitation, communication mediaincludes wired media such as a wired network or direct-wired connection,and wireless media such as acoustic, radio frequency (RF), infrared andother wireless media. Combinations of any of the above can also beincluded within the scope of computer-readable media.

FIG. 1 is a block diagram of an example of a computing system 100capable of implementing embodiments of the present disclosure. Computingsystem 100 broadly represents any single or multi-processor computingdevice or system capable of executing computer-readable instructions.Examples of computing system 100 include, without limitation,workstations, laptops, client-side terminals, servers, distributedcomputing systems, handheld devices, or any other computing system ordevice. In its most basic configuration, computing system 100 mayinclude at least one processor 110 and a system memory 140.

Both the central processing unit (CPU) 110 and the graphics processingunit (GPU) 120 are coupled to memory 140. System memory 140 generallyrepresents any type or form of volatile or non-volatile storage deviceor medium capable of storing data and/or other computer-readableinstructions. Examples of system memory 140 include, without limitation,RAM, ROM, flash memory, or any other suitable memory device. In theexample of FIG. 1, memory 140 is a shared memory, whereby the memorystores instructions and data for both the CPU 110 and the GPU 120.Alternatively, there may be separate memories dedicated to the CPU 110and the GPU 120, respectively. The memory can include a frame buffer forstoring pixel data that drives a display screen 130.

The system 100 includes a user interface 160 that, in oneimplementation, includes an on-screen cursor control device. The userinterface may include a keyboard, a mouse, and/or a touch screen device(a touchpad).

CPU 110 and/or GPU 120 generally represent any type or form ofprocessing unit capable of processing data or interpreting and executinginstructions. In certain embodiments, processors 110 and/or 120 mayreceive instructions from a software application or hardware module.These instructions may cause processors 110 and/or 120 to perform thefunctions of one or more of the example embodiments described and/orillustrated herein. For example, processors 110 and/or 120 may performand/or be a means for performing, either alone or in combination withother elements, one or more of the monitoring, determining, gating, anddetecting, or the like described herein. Processors 110 and/or 120 mayalso perform and/or be a means for performing any other steps, methods,or processes described and/or illustrated herein.

In some embodiments, the computer-readable medium containing a computerprogram may be loaded into computing system 100. All or a portion of thecomputer program stored on the computer-readable medium may then bestored in system memory 140 and/or various portions of storage devices.When executed by processors 110 and/or 120, a computer program loadedinto computing system 100 may cause processor 110 and/or 120 to performand/or be a means for performing the functions of the exampleembodiments described and/or illustrated herein. Additionally oralternatively, the example embodiments described and/or illustratedherein may be implemented in firmware and/or hardware.

Accordingly, embodiments of the present invention provide forco-browsing using various architectures, wherein the co-browsingfunctionality is embedded in content of a content provider and/orincluded in an extension to a browser used by one of the participants ina co-browse session.

Co-browsing of online content is implemented through variousarchitectures. For instance, a business-to-customer (B2C) architectureprovides for co-browsing of online content hosted by a participating website between a customer and an agent of the web site, wherein theco-browsing functionality is embedded within content provided by aparticipating content provider, and wherein the agent acting as a guestinitiates the co-browse session. A business-to-customer-to-customer(B2C2C) architecture provides for co-browsing of online content hostedby a participating web site between multiple participants, wherein theco-browsing functionality is embedded within content provided by aparticipating content provider, and wherein one participant acting as ahost initiates the co-browse session. A customer-to-customer (C2C)architecture provides for co-browsing of online content between a one ormore participants with only the participant acting as a host having anextension to their web browser configured for implementing co-browsing.

B2C Architecture with Co-Browsing Functionality Embedded in OnlineContent, and where the Guest Initiates the Co-Browsing Session

FIG. 2 is an illustration of an information flow diagram showing theflow of information through a co-browse system 200 that is capable ofestablishing a co-browse session between two parties (e.g., a customerand an agent of a business) through co-browsing functionality embeddedin content provided by a content provider, in accordance with oneembodiment of the present disclosure. System 200 illustrates a B2Carchitecture that provides for co-browsing of online content hosted by acontent provider (referred to as “.com”) between a customer C1 210 andan agent 220 of the content provider (e.g., business), wherein theco-browse session is initiated by the guest agent 220, and wherein thecustomer C1 210 acts as the host of the co-browse session.

For instance, a co-browsing session may be established between a webbrowser running on a computer system associated with customer C1 210,and a web browser running on a computer system associated with agent 220that is affiliated with the business associated with .com server 230.The co-browsing session allows the two browsers to display substantiallythe same online content (e.g., an html web page), with somemodifications for co-browsing depending on whether it is the host or theguest. In this embodiment, no extension application to any web browseris added to either of the computer systems associated with the customerC1 210 or the agent 220 used for facilitating the co-browsing session.

A use case for the B2C architecture may involve an insurance company anda customer, wherein the customer is trying to navigate through theinsurance company's web site. For instance, the customer may be tryingto fill out an accident form through the web site. The customer isalready logged onto the insurance company's web site. The customer mayencounter some problems filling out the form, and may initiate secondarycommunication (e.g., voice or chat) with the agent of the insurancecompany. The agent is able to initiate a co-browse session, throughwhich the agent is able to help the customer fill out the form.

As shown in FIG. 2, a communication session is established between thecostumer C1 210 and the .com server 230 in step 1, wherein server 230instantiates the .com website in order to provide content. For instance,the browser at C1 210 is able to receive content from .com server 230,wherein the content includes embedded co-browsing functionality (e.g.,html, JavaScript, cascading style sheets [CSS], etc.) that is enabledwhen activated. For example, the online content includes code, images,video, or other content related to a web page. Access to the content isaccomplished through some communication network (not shown), such as,the internet. When the content is delivered to C1 210, the co-browsingfunctionality is enabled at the appropriate time to facilitateco-browsing between C1 210 and the agent 220.

As previously described, the customer may enlist the help of the agentto help navigate through the content provided by .com server 230, atstep 2. This help may be implemented through a secondary communicationsession, such as, a voice channel, a chat channel, etc. Through thesecondary channel, C1 210 is also able to inform the agent of variousforms of identifying information, such as a user name known ordiscoverable by the .com server 230. When the agent determines that aco-browse session would be helpful, the agent initiates a co-browsesession at step 3 with the co-browse communication server 250, whereinthe agent initiator acts as the guest in the co-browse session becauseC1 210 as host already has a browser session with .com 230. After theco-browse session is initiated and established, the co-browsecommunication server 250 sends back the co-browse session identifier toagent 220.

At step 4, the agent 220 delivers the co-browse session identifier to.com server 230, along with user identifier information. Because thecustomer C1 210 is logged onto .com server 230, the user identifierinformation is parsed and cross-referenced with information in database235 (e.g., user profile and session identifiers) to determine thebrowser session established between C1 210 and the co-browsecommunication server 250 at step 5.

At step 6 and after determining which session is established between C1210 and .com server 230, the .com server 230 is able to enable theco-browsing functionality in the content delivered to C1 120. Forexample, a flag 241 is set that now exposes a start icon 245 orhyperlink within the content. In one embodiment, the co-browsefunctionality is embedded in the content through an “allow co-browse”tag 243 (e.g., html, JavaScript, cascading style sheets [CSS], etc.).

At step 7, when the start icon 245 is activated, the web browser at C1210 is directed to the co-browse communication server 250 in order tojoin C1 210 into the existing co-browse session.

For instance, the start icon 245 includes a link to the co-browsecommunication server 250. By instantiating the link through theactivation of the start icon 245, the co-browse session is established,such that the co-browse session couples the browser of C1 210 to thecommunication server 250 through a communication network, and couplesthe web browser at agent 220 to the co-browse communication server 250.In another embodiment, the hyperlink is associated with some icon orwidget that is provided on every page of the online content from .com230. Clicking on the icon or hyperlink joins C1 210 into the co-browsesession through the communication server 250.

In this co-browse session, the communication server 250 acts as aninterface between the web browsers for C1 210 and the agent 220. Inaddition, the co-browsing functionality is embedded within the contentdelivered to both C1 210 and agent 220. As long as both are displayingcontent from .com server 230, the co-browse functionality is executingand the co-browse session remains live. As such, neither C1 210 or agent220 needs an extension implementing co-browsing on their correspondingbrowsers, since the co-browsing functionality is embedded into thecontent provided by the .com server 230.

In addition, in the co-browse session whatever online content providedto the browser for C1 210 by .com server 230 is forwarded to thecommunication server 250, and then delivered to the browser for theagent 220. In this manner, the browser for the agent 220 is insulatedfrom .com server 230, and relays all communication with .com server 230through the communication server 250 and the browser for C1 210.Further, control (e.g., cursor click) or navigation information (e.g.,cursor position and interaction) depending on priority and/or rulessettings as implemented at C1210 is relayed to the communication server250, and to the agent 220.

In addition, any action on the online content as interfaced by thebrowser for the agent 220 is not directly delivered to the .com server230, and instead is delivered to the communication server 250, whichthen delivers the interaction instruction to the browser of C1 210. Atthat point, the browser of C1 210 will deliver the interactioninstruction to the .com server 230. In that manner, the instructioncomes from the browser at C1 210, though it originated from the browserat agent 220. Further, any control (e.g., cursor click) or navigationinformation (e.g., cursor position and interaction) as interfaced bybrowser at agent 220, which depending on priority and/or rules settingsimplemented at agent 220, is then relayed to .com server 230.

In some embodiments, the communication server and/or the agentestablishes a communication link back to the .com website forsynchronizing the online content appearing on the displays for C1 andthe agent.

Again, if the communication server malfunctions, then the communicationsession between the browser of C1 210 and the .com server 230 isunaffected. That is, only the link between the browser at the agent andthe communication server will be affected (e.g., go down).

FIG. 3A is a flow diagram 300A illustrating steps in a method forproviding co-browsing between two parties through co-browsingfunctionality embedded in content provided by a content provider, inaccordance with one embodiment of the present disclosure. In otherembodiments, all or portions of the method outlined in flow diagram 300Amay be implemented as a computer-implemented method; or implemented asinstructions within a computer system including a processor and memoryconfigured to execute the instructions; or implemented ascomputer/processor executable instructions stored on a non-transitorycomputer-readable storage medium. Some or all of the operationsperformed in diagram 300A are implementable within apparatus 100 and/orco-browse system 200 of FIG. 2.

At 310, the method includes establishing a first communication sessionbetween a first web browser of first device (e.g., a customer) and acontent provider (e.g., a business and/or .com server) over acommunication network. The session is established to deliver content tothe first web browser from the content provider, wherein the content isembedded with co-browsing functionality (e.g., html, JavaScript, CSS,etc.). The first device is associated with a first user. In oneembodiment, the first user is logged into the content provider, suchthat the first user is authenticated through a log-in process and thefirst user is associated with the user identifier. In that manner, thefirst communication session is discoverable by cross referencing theuser identifier.

At 320, the method includes establishing a second communication sessionbetween a second device (e.g., agent of the business) and a co-browsecommunication server to initiate a co-browse session, wherein theco-browse session comprises a co-browse session identifier. Forinstance, in the example previously given, the customer is enlisting thehelp of an agent to help navigate through a form provided by a web pageas content through a co-browse session. This may occur through asecondary communication channel (e.g., chat or voice), wherein thecustomer may relay user identifying information to the agent). That is,a fourth communication session is established between the first user anda second user of the second device, wherein the user identifier of thefirst user is communicated and/or delivered to the second user throughthe fourth communication session. In this particular case, the seconddevice acts as a guest in the co-browse session even though the seconddevice initiates the co-browse session. In most cases, it is the hostthat already has the browser session with the content provider overwhich content is delivered.

When the co-browse session is established, the co-browse communicationserver delivers the co-browse session identifier to the second device(e.g., agent). In that manner, the session identifier can be used tojoin other participants. For example, at 330, the method includessending a user identifier, associated with the first user, and theco-browse session identifier from the second device to the contentprovider. The user identifier may be a user name known or discoverableby the content provider. The content provider can then use that useridentifier to cross reference and discover the first communicationsession delivering content to the first web browser associated with thefirst user.

Once that browser session is identified, content delivered to the firstweb browser may be modified to enable the co-browsing functionality. Inparticular, at 340, the method includes exposing the co-browsingfunctionality in the content delivered to the first web browser with anicon comprising the co-browse session identifier, such that when theicon is activated at the first device, the first web browser is joinedinto the co-browse session initiated by the second device (e.g., agent).The first communication session can be identified at the contentprovider based on the previously received user identifier, such as,through cross-referencing information in the database maintained by thecontent provider. Once the session is identified, its correspondingcontent can be accessed in order to enable the co-browsingfunctionality. As previously described, the co-browsing functionality isembedded in the content delivered to the first web browser, and enabled(e.g., by setting a flag), thereby exposing the co-browse functionality(e.g., through a start icon, or hyperlink, etc.). In one implementation,a new page is generated for the content, wherein the new page has theco-browse functionality enabled and includes the start icon. The newpage is delivered as content to the first web browser.

At 350, the method includes establishing the co-browse session betweenthe first web browser of the first device as a host and a second webbrowser of the second device, such that content at the first web browseris delivered to the second web browser of the second device via theco-browse communication server through the co-browse session. Forexample, a document object model (DOM) of the content is accessed at thefirst web browser, and the DOM is delivered to the co-browsecommunication server for delivery to the second web browser. In thatmanner, the co-browse session allows the two browsers to displaysubstantially the same online content (e.g., an web page comprisinghtml, JavaScript, CSS, etc.), with some modifications for co-browsingdepending on control and priority information as defined for the host orthe guest. For instance, changes to the DOM are recognized at one of theweb browsers of the first and second devices. The changes may includeevents (e.g., mouse/cursor movement, mouse clicks, etc.). These changesare updated in the DOM, wherein the updated DOM is delivered to theother web server through the co-browse communication server.

More particularly, the second web browser is joined into the co-browsesession to establish the co-browse session based on the co-browsesession identifier. For instance, the method includes determining thatthe icon is activated at the first device, thereby indicating that thefirst user is requesting to join the co-browse session, in this case asthe host. A third communication session is established between the firstweb browser and the co-browse communication server, such as, through thehyperlink that is instantiated by activating the start icon. Because thestart icon includes the co-browse session identifier, that identifier isdelivered from the first web browser to the co-browse communicationserver in a request to join the co-browse session. The communicationserver then joins the first web browser into the co-browse session basedon the co-browse session identifier.

In one embodiment, a rules engine is established at the first device. Inone implementation, the rules engine filters out sensitive information,such that it is prevented from being delivered to the co-browsecommunication server, and ultimately to the second web browser at thesecond device. For example, the customer at the first device may enterin a sensitive banking information in the form provided by the .comserver. Because the first device acts as the host, that sensitiveinformation would need to be ultimately delivered to the .com server forprocessing; however, the sensitive information may be not needed by thesecond user (e.g., agent) at the second device. To prevent fraud, thatsensitive information is identified and prevented from being deliveredto the co-browse communication server.

FIG. 3B is a flow diagram 300B illustrating steps in a method forproviding co-browsing between two parties by a participating contentprovider, and more specifically though co-browsing functionalityembedded in content provided by the content provider, in accordance withone embodiment of the present disclosure. In other embodiments, themethod outlined in flow diagram 300B may be implemented as acomputer-implemented method; or implemented as instructions within acomputer system including a processor and memory configured to executethe instructions; or implemented as computer/processor executableinstructions stored on a non-transitory computer-readable storagemedium. Some or all of the operations performed in diagram 300A areimplementable within apparatus 100 and/or co-browse system 200 of FIG.2.

At 360, the method includes establishing a first communication sessionbetween a content provider (e.g., a business and/or .com server) and afirst web browser of first device (e.g., a customer) over acommunication network. The session is established to deliver content tothe first web browser from the content provider, wherein the content isembedded with co-browsing functionality (e.g., html, JavaScript, CSS,etc.). The first device is associated with a first user.

At 370, the method includes delivering content to the first web browser,wherein the content comprises embedded co-browsing functionality (e.g.,html, JavaScript, CSS, etc.).

At 380, the method includes receiving a first user identifier associatedwith the first user and a co-browse session identifier of a co-browsesession from a second device. The second device is joined into theco-browse session as a guest. Specifically, the first user (e.g.,customer) may be conducting a secondary communication with a second user(e.g., agent) associated with the second device, and wherein the seconduser is initiating a co-browse session in order to help the first usernavigate through the content. In that secondary communication, the firstuser identifier may be transferred. In the meantime, the second deviceis implemented to initiate a co-browse session.

At 390, the method includes exposing the co-browsing functionality inthe content with an icon comprising the co-browse session identifier.When the icon is activated at the first device, the first web browser isjoined into the co-browse session as a host. Previously, the second webbrowser had already joined the co-browse session upon initiation. Whenthe co-browse session is established between the first web browser andthe second web browser through a co-browse communication server, thecontent at the first web browser is delivered to the second web browservia the co-browse communication server.

TABLE 1 LISTING OF CLAIMS 1. A method for co-browsing, comprising;establishing a first communication session between a first web browserof first device and a content provider over a network to deliver contentto said first web browser from said content provider, wherein said firstdevice is associated with a first user, wherein said content comprisesembedded co-browsing functionality; establishing a second communicationsession between a second device and a co- browse communication server toinitiate a co-browse session, wherein said co-browse session comprises aco-browse session identifier, wherein said second device acts as a guestin said co-browse session; sending a user identifier associated withsaid first user and said co-browse session identifier from said seconddevice to said content provider; exposing said co-browsing functionalityin said content delivered to said first web browser with an iconcomprising said co-browse session identifier, such that when said iconis activated at said first device, said first web browser is joined intosaid co-browse session; establishing said co-browse session between saidfirst web browser of said first device as a host and a second webbrowser of said second device, such that said content at said first webbrowser is delivered to said second web browser of said second devicevia said co-browse communication server through said co-browse session.2. The method of Claim 1, wherein said establishing said co-browsesession further comprises: determining that said icon is activated atsaid first device; establishing a third communication session betweensaid first web browser and said co-browse communication server;delivering said co-browse session identifier from said first web browserto said co-browse communication server in a request to join saidco-browse session; and joining said first web browser into saidco-browse session based on said co- browse session identifier. 3. Themethod of Claim 1, wherein said exposing said co-browsing functionalityfurther comprises: identifying said first communication session at saidcontent provider based on said user identifier; accessing said content;and enabling said co-browsing functionality in said content. 4. Themethod of Claim 3, further comprising: setting a flag that enables saidco-browse functionality; generating a new page for said content that isenabled with said co-browse functionality, wherein said new pagecomprises said icon; and delivering said new page of said content tosaid first web browser. 5. The method of Claim 1, further comprising:establishing a fourth communication session between said first user anda second user of said second device; and communicating said useridentifier of said first user to said second user through said fourthcommunication session. 6. The method of Claim 5, wherein said fourthcommunication session comprises voice communication. 7. The method ofClaim 1, wherein said establishing a second communication sessionfurther comprises: sending said co-browse session identifier from saidco-browse communication server to said second web browser. 8. The methodof Claim 1, wherein said establishing a first communication sessionfurther comprises: authenticating said first user in a log-in process;and associating said first user with said user identifier. 9. The methodof Claim 1, further comprising: joining said second web browser intosaid co-browse session based on said co- browse session identifier. 10.The method of Claim 1, wherein said co-browse functionality in saidcontent provides for: accessing a document object model (DOM) of saidcontent delivered to said first web browser; and sending said DOM tosaid co-browse communication server for delivery to said second webbrowser. 11. The method of Claim 10, further comprising: recognizingchanges to said DOM in an updated DOM at one of said first and secondweb browsers; and sending said updated DOM to said co-browsecommunication server for delivery to the other of said first and secondweb browsers. 12. The method of Claim 1, further comprising: enabling arules engine at said first device to filter sensitive information, suchthat said sensitive information is not delivered to said co-browsecommunication server. 13. A system for co-browsing, comprising: a firstdevice comprising a first web browser configured for communicating overa network, wherein said first device is associated with a first user; acontent provider providing content comprising embedded co-browsingfunctionality; a first communication session between said first webbrowser of said first device and said content provider over said networkconfigured to deliver content to said first web browser from saidcontent provider; a second device comprising a second web browser forcommunicating over said network; a co-browse communication server (CS)configured to provide a co-browse session comprising a co-browse sessionidentifier; a second communication session between said second deviceand said co-browse communication server to initiate said co-browsesession, wherein said second device acts as a guest in said co-browsesession; and wherein said co-browse session is established between saidfirst web browser of said first device as a host and a second webbrowser of said second device through said embedded co-browsingfunctionality, such that said content at said first web browser isdelivered to said second web browser of said second device via saidco-browse communication server through said co-browse session. 14. Thesystem of Claim 13, further comprising: a third communication sessionbetween said second device and said content provider for delivering saiduser identifier and said co-browse session identifier to said contentprovider; wherein said co-browsing functionality in said contentdelivered to said first web browser is exposed with an icon comprisingsaid co-browse session identifier, such that when said icon is activatedat said first device, said first web browser is joined into saidco-browse session; 15. The system of Claim 13, wherein said first webbrowser is configured to deliver said co-browse session identifier tosaid co-browse communication server in a request to join said co-browsesession, and wherein said co-browse communication server is configuredto join said first web browser in said co-browse session based on saidsession identifier. 16. The system of Claim 13, wherein said contentprovider is configured to identify said first communication sessioncomprising said content based on said user identifier, and to enablesaid co-browsing functionality in said content. 17. The system of Claim13, further comprising: a fourth communication session between saidfirst user and a second user of said second device, wherein said fourthcommunication session is configured for communicating said useridentifier to said second user. 18. The system of Claim 13, wherein saidco-browse communication server is configured to send said co-browsesession identifier to said second web browser for purposes of initiatingsaid co-browse session. 19. The system of Claim 13, further comprising:a rules engine at said first device configured to filter sensitiveinformation, such that said sensitive information is prevented frombeing delivered to said co-browse communication server. 20. A method forco-browsing, comprising: establishing a first communication sessionbetween a content provider and a first web browser of a first deviceover a network, wherein said first device is associated with a firstuser; delivering content to said first web browser, wherein said contentcomprises embedded co-browsing functionality; receiving a first useridentifier associated with said first user and a co-browse sessionidentifier of a co-browse session from a second device, wherein saidsecond device is joined into said co-browse session as a guest; andexposing said co-browsing functionality in said content with an iconcomprising said co-browse session identifier, such that when said iconis activated at said first device, said first web browser is joined intosaid co-browse session as a host, wherein when said co-browse session isestablished between said first web browser and said second web browserthrough a co-browse communication server said content at said first webbrowser is delivered to said second web browser via said co-browsecommunication server. 21. The method of Claim 20, further comprising:identifying said first communication session based on said useridentifier; accessing said content; and enabling said co-browsingfunctionality in said content.B2C2C Architecture with Co-Browsing Functionality Embedded in OnlineContent, and where the Host Initiates the Co-Browsing Session

FIG. 4 is an illustration of an information flow diagram showing theflow of information through a co-browse system 400 that is capable ofestablishing a co-browse session between at least two parties (e.g., twoor more participants) through co-browsing functionality embedded incontent provided by a content provider, in accordance with oneembodiment of the present disclosure. Co-browsing allows participants tosimultaneously view the content within a co-browse session. In addition,because the co-browsing functionality is hosted by the content provider,none of the participants are required to have a co-browsing extension ontheir respective browsers.

System 400 illustrates a B2CC2C architecture that provides forco-browsing of online content by at least two participants. The onlinecontent is delivered by a content provider (referred to as “.com”)through a server 430 to a host participant HP 410. A co-browsing sessionmay be established between a web browser running on a computerassociated with the host participant HP 410, and a web browser runningon a computer system associated with a guest participant GP 420A.Additional guest participants GP 420A-N may also be included in theco-browse session. In particular, participant HP 410 acts as a host inthe co-browse session, initiates the co-browse session, and invitesguest participants GP 420A-N into the co-browse session. The co-browsingsession allows the browsers of participating parties to displaysubstantially the same online content (e.g., an html web page), withsome modifications for co-browsing depending on whether the participantis the host or the guest.

A possible use case illustrating the implementation of the B2C2Carchitecture providing a co-browse session may be online shopping by twoor participants at a .com website of a content provider, wherein theco-browse session is supported by the content provider. For example,host participant HP 410 may be shopping on the .com website, and findsan appealing item. Participant HP 410 may want some input on the item bya friend GP 420A, almost as if the two participants were shoppingtogether at a store in a local shopping mall. As such, host participantHP 410 selects the co-browsing feature on the website, as provided bythe content provider, initiates the co-browse session, and invites guestparticipant GP 420A. After participant GP 420A joins, both participantsare able to view the consent through a shared shopping experienceprovided by the co-browse session. Additional guests may be similarlyjointed into the same co-browse session.

As shown in FIG. 4, a communication session is established between hostparticipant HP 410 and the .com server 430 in step 1A, wherein server430 instantiates the .com website and provides content (including code,images, video, or other content related to a web page). For instance,the browser at HP 410 is able to receive content from .com server 430,wherein the content includes embedded co-browsing functionality (e.g.,html, JavaScript, cascading style sheets [CSS], etc.) that is enabledupon activation. Access to the content is accomplished through somecommunication network (not shown), such as, the internet. Theco-browsing functionality is enabled at the appropriate time tofacilitate co-browsing between the host participant HP 410 and the guestparticipants GP 420A-N.

The co-browse functionality is embedded within the content delivered tothe browser at host participant HP 410 at step 1A. For example, theco-browse functionality is embedded in the content through an “allowco-browse” tag 443 (e.g., html, JavaScript, CSS, etc.). In oneembodiment, the co-browse functionality is provided on every page of thecontent. For example, the content provider supports a co-browsingfeature that allows any visitor to its website to initiate a co-browsesession and invite one or more guests to join the session. The co-browsesession enables a shared shopping experience between the participants.Because the co-browsing functionality is provided within the content, aco-browse session continues to exist as long as the participants areaccessing the content from .com server 430 through their respectivebrowsers. That is, no browser extension providing co-browsingfunctionality is necessary to be downloaded at the participants computersystems, since the co-browsing functionality is embedded into thecontent provided by the .com server 430.

A start icon or widget 445 may also be provided within the deliveredcontent. In one embodiment, the start icon is provided on every page ofthe content provided by server 430. For example, the start icon 445 mayinclude a hyperlink. At step 2, by activating icon 445, the web browserat host participant HP 410 is directed to the co-browse communicationserver 450 through the hyperlink in order to initiate a co-browsesession, and join the browser at host participant HP 410 into theco-browse session. For instance, host participant HP 410 would like toshare an item with an invited guest through a co-browse session. Oncethe co-browse session is established, the browser at host participant HP410 is coupled to the communication server 450 through a communicationnetwork.

The co-browse session is associated with a co-browse session identifierthat is generated by the communication server 450 once the co-browsesession is established. At step 3, the co-browse communication serversends the co-browse session identifier back to the host participant HP410. In that manner, host HP 410 can invite one or more guests bypassing the co-browse session identifier to the guests.

At step 4, an invitation to join the co-browse session is delivered toone or more guest participants GP 420A-N. The invitation includes theco-browse session identifier or some information that can be mapped backto the session identifier. The invitation may be in the form of anelectronic communication (e.g., email, chat, voice, etc.) that includesor allows for the transfer of the co-browse session identifier orcorresponding information. For example, an invitation to co-browse maybe delivered via email, wherein the email may include a link to a URL toestablish the co-browsing session. In another implementation, aninvitation to co-browse is delivered via copying a URL. That is, the URLis delivered, and the guest goes to that URL to initiate the co-browsesession. In still another implementation, the invitation to co-browse isdelivered via a message on a social networking platform. In some cases,the invitation may be some analog form of communication, such as awritten note including a token, wherein the token is used toauthenticate and/or identify the co-browse session.

For example, the co-browse session identifier may be included in ahyperlink 460 (e.g., short URL) that is included in the invitation. Whenthe hyperlink is selected by a guest participant, the correspondingbrowser is directed to the co-browse communication server 450. Becausethe hyperlink includes the co-browse session identifier, the co-browsecommunication server is able to join the corresponding browser into theproper co-browse session.

In another embodiment, the co-browse session identifier is linked withor is included within a token (e.g., password and/or session identifierindicating which co-browse session is to be used). The token may bedelivered via any mechanism, such as, the phone, email, etc. along withinstructions for using that token to join the co-browse session. Forinstance, the guest presents the token to the back end server that isfacilitating the co-browse session. The token is used to identify thesession and the host computer. As such, the token may be communicatedthrough any means, such as through voice communication in step 4. Forexample, the host participant HP 410 may call guest participant GP 420Aand through voice communication transfer the token to guest GP 420A. Inaddition, the host HP 410 may give instructions on how to join theco-browse session, such as accessing a web site with a join page, andinputting the token into the join page 470. For example, at step 5, whenthe token is presented at a co-browse join page 470, the correspondingbrowser (e.g., of a guest participant GP 420A) is directed or redirectedto the co-browse communication server 450 and joined into the associatedco-browse session. In one implementation, the join page 470 is locatedat the website supported by .com server 430. In another implementation,the join page 470 is provided by the communication server 450. In stillanother implementation, the join page may be located at a separatenetwork location.

In still another embodiment, the invitation to join the co-browsesession may be through a co-browsing social networking platform or anythird party social networking platform (e.g., Facebook, Twitter, Skype,etc.), wherein both parties are logged into the corresponding socialnetwork. In this case, the host participant HP 410 may invite guestparticipant GP 420A through come communication channel provided by thesocial network. As an illustration, the host participant may send amessage (e.g., post, mail, etc.) to the home or message page of theguest GP 420A, wherein the message includes the link to join theco-browse session. In another illustration, the host participant HP 410and the guest may be chatting through the social networking site.

The co-browse session is fully established when the guest GP 420A joins,such that the co-browse session couples the browser of the hostparticipant HP 410 to the co-browse communication server 450 through acommunication network, and couples the web browser at the guest GP 420Ato the co-browse communication server 450 through the network.

The co-browse communication server 450 acts as an interface between theweb browsers for host HP 410 and guest GP 420A, and allows the twobrowsers to display substantially the same online content (e.g., an htmlweb page). For example, in the co-browse session whatever online contentprovided to the browser for host HP 410 by .com server 430 is forwardedto the communication server 450, and then delivered to the browser forthe guest GP 420A. Further, control (e.g., cursor click) or navigationinformation (e.g., cursor position and interaction) depending onpriority and/or rules settings as implemented at host HP 410 is relayedto the communication server 450, and then to the guest GP 420A.

In this manner, the guest GP 420A is insulated from the .com server 430,and relays all communication to or with .com server 430 through thecommunication server 450 and the host HP 410. For example, any action onthe online content as interfaced by the browser for the guest GP 420A isnot directly delivered to the .com server 430, and instead is deliveredto the communication server 250, which then delivers the interactioninstruction to the browser at the host HP 410. At that point, thebrowser at host HP 410 will deliver the interaction instruction to the.com server 430. In that manner, the instruction comes from the browserat host HP 410, even though it originated from the browser at guest GP420A. Further, any control (e.g., cursor click) or navigationinformation provided by the guest GP 420A is relayed to thecommunication server 450 and then to the host HP 410 depending onpriority and/or rules settings as implemented at the guest GP 420A.

Again, if the communication server 450 malfunctions, then thecommunication session between the browser of host participant HP 410 andthe .com server 450 is unaffected. That is, only the link between thebrowser at guest GP 420A and the communication server 450 will beaffected (e.g., experience lower performance, terminate, etc.).

FIG. 5 is a flow diagram illustrating steps in a method for providingco-browsing between two or more parties through co-browsingfunctionality embedded in content provided by a content provider, inaccordance with one embodiment of the present disclosure. In otherembodiments, all or portions of the method outlined in flow diagram 500may be implemented as a computer-implemented method; or implemented asinstructions within a computer system including a processor and memoryconfigured to execute the instructions; or implemented ascomputer/processor executable instructions stored on a non-transitorycomputer-readable storage medium. Some or all of the operationsperformed in diagram 500 are implementable within apparatus 100 and/orco-browse system 400 of FIG. 4.

At 510, the method includes establishing a first communication sessionbetween a first web browser of first device (e.g., host participant) anda content provider over a network. The session is established to delivercontent to the first web browser from the content provider, wherein thecontent includes embedded co-browsing functionality (e.g., html,JavaScript, CSS, etc.).

At 520, the method includes receiving a request for activating theco-browsing functionality at the first device. For example, the requestmay be in the form of a hyperlink displayable within or overlaid thecontent, that when selected initiates the joining to the co-browsesession. In one embodiment, the hyperlink is instantiated within anicon. Prior to activation, the co-browsing functionality as deliveredwith the content runs in the background but is not implemented. Aspreviously described, a host participant at the first device may want tohave a shared web experience (e.g., shopping), and initiates theco-browsing session by selecting a co-browsing start icon provided withthe content.

After determining that the start co-browse session icon is activated atthe first device, at 530 the method includes establishing a secondcommunication session between the first web browser and the co-browsecommunication server. As such, the co-browse communication serverinitiates and/or establishes the co-browse session including a co-browsesession identifier and joins the first web browser into the co-browsesession. In this embodiment, the first device acts as the host in theco-browse session, wherein the host maintains the original browsersession with the content provider to receive content, and wherein thehost initiates the co-browse session.

In addition, after the co-browse session is established, the co-browsecommunication server delivers the co-browse session identifier to thefirst device (e.g., host participant). In that manner, the sessionidentifier can be used to join other guest participants. As previouslydescribed, an invitation that includes some mapping reference to theco-browse session identifier is delivered to guests in order to join webbrowsers associated with those guests to the co-browse session. Theinvitation is in the form of an electronic communication (e.g., email,chat, voice, etc.) that allows for the transfer of the co-browse sessionidentifier, or some other information used to map back to the sessionidentifier. In some cases, the invitation may be some analog form ofcommunication, such as a written note including a token.

For example, the invitation may include a hyperlink (e.g., short URL)that includes the session identifier, wherein the hyperlink directs thecorresponding browser to the co-browse communication server in order tojoin that browser to the co-browse session associated with the co-browsesession identifier. That is, the co-browse communication servergenerates the hyperlink including some reference to the co-browsesession identifier, that when delivered to and selected by a seconddevice is used to join the second device into the co-browse session. Forexample, the hyperlink for joining the co-browse session may bedelivered within an email sent to or accessible by the second device, orwithin a chat window conducted between the first and second devices.

In other embodiments, a token is used to join the co-browse sessionthrough any join page. For example, a fourth communication session maybe established between the second web browser and the join page. Thetoken is entered into the join page, wherein the token may be a passwordthat indicates which co-browse session is to be used. When the token isauthenticated, the corresponding browser is directed to the co-browsecommunication server (e.g., through the third communication session),and is joined into the proper co-browse session based on informationcontained in the token. In still other embodiments, the invitation tojoin the co-browse session is made through a messaging or communicationfeature of a social network platform (e.g., co-browsing social network,or third party social network [e.g., Facebook, Twitter, Skype, etc.]).

Once the invitation to join the co-browse session is accepted by theguest (activate the join link, or enter token in join page), at 540 themethod includes establishing a third communication session between asecond web browser of a second device (e.g., associated with the guest)and the co-browse communication server to send a request to join theassociated co-browse session, and subsequently to join the second webbrowser into the co-browse session based on the co-browse sessionidentifier. Because the request includes some reference to the co-browsesession identifier, as previously described, the communication server isable to identify the proper co-browse session, and join the second webbrowser into the co-browse session.

At 550, the method includes establishing the co-browse session betweenthe first web browser as the host and the second web browser of thesecond device as a guest, such that content at the first web browser isdelivered to the second web browser via the co-browse communicationsever over the co-browse session. For example, a DOM (e.g., includinghtml, JavaScript, CSS, etc.) of the content is accessed at the first webbrowser and delivered to the co-browse communication server for deliveryto the second web browser. The co-browse session allows the two browsersto display substantially the same DOM, with some modifications forco-browsing depending on control and priority information as defined forthe host or the guest. For instance, changes to the DOM are recognizedat one of the web browsers of the first and second devices. The changesmay include events (e.g., mouse/cursor movement, mouse clicks, etc.).These changes are updated in the DOM, wherein the updated DOM isdelivered to the other web server through the co-browse communicationserver.

TABLE 2 LISTING OF CLAIMS 1. A method for co-browsing, comprising;establishing a first communication session between a first web browserof first device and a content provider over a network to deliver contentto said first web browser from said content provider, wherein saidcontent comprises embedded co-browsing functionality; receiving arequest for activating said co-browsing functionality at said firstdevice; establishing a second communication session between said firstweb browser and a co-browse communication server to initiate a co-browsesession, wherein said co- browse session comprises a co-browse sessionidentifier, wherein said first device acts as a host in said co-browsesession; establishing a third communication session between a second webbrowser of a second device and said co-browse communication server tojoin said second web browser into said co-browse session based on saidco-browse session identifier; establishing said co-browse sessionbetween said first web browser as said host and said second web browserof said second device as a guest, such that said content at said firstweb browser is delivered to said second web browser via said co-browsecommunication sever over said co-browse session. 2. The method of Claim1, wherein said receiving a request for activating said co-browsingfunctionality further comprises: providing an icon for activating saidco-browsing functionality within or overlaid said content at said firstdevice. 3. The method of Claim 2, wherein said establishing a secondcommunication session comprises: determining that said icon is activatedat said first device; and initiating said co-browse session; and joiningsaid first web browser into said co-browse session. 4. The method ofClaim 1, wherein said co-browse functionality in said content providesfor: accessing a document object model (DOM) of said content deliveredto said first web browser; and sending said DOM to said co-browsecommunication server for delivery to said second web browser. 5. Themethod of Claim 4, further comprising: recognizing changes to said DOMin an updated DOM at one of said first and second web browsers; andsending said updated DOM to said co-browse communication server fordelivery to the other of said first and second web browsers. 6. Themethod of Claim 1, further comprising: receiving a link comprising saidco-browse session identifier at said first web browser from saidco-browse communication server, wherein said link when activated directsa corresponding browser to establish communication with said co-browsecommunication server to join said co-browse session; and delivering saidlink to said second device. 7. The method of Claim 6, wherein saiddelivering said link comprises: pasting said link into a chat conductedbetween said first device and said second device. 8. The method of Claim6, wherein said delivering said link comprises: including said link inan electronic message that is delivered from said first device to saidsecond device. 9. The method of Claim 6, wherein said establishing athird communication session comprises: activating said link at saidsecond device. 10. The method of Claim 1, wherein said establishing athird communication session comprises: establishing a fourthcommunication session between said second web browser and a join page;entering a token in said join page, wherein said token comprises saidco-browse session identifier; and directing said second web browser tosaid co-browse communication server over said third communicationsession to join said second web browser into said co-browse sessionbased on said token. 11. A system for co-browsing, comprising: a firstdevice comprising a first web browser configured for communicating overa network; a content provider providing content comprising embeddedco-browsing functionality; a first communication session between saidfirst web browser and said content provider over said network to deliversaid content to said first web browser from said content provider; asecond device comprising a second web browser for communicating oversaid network; a co-browse communication server configured to provide aco-browse session comprising a co-browse session identifier; a secondcommunication session established between said first web browser andsaid co-browse communication server to initiate said co-browse sessioncomprising a co- browse session identifier, wherein said secondcommunication session is established in response to receiving a requestfor activating said co-browse functionality at said first device,wherein said first device acts as a host in said co-browse session; athird communication session established between said second web browserand said co-browse communication server to join said second web browserinto said co- browse session based on said co-browse session identifier;said co-browse session established between said first web browser assaid host and said second web browser of said second device as a guest,such that said content at said first web browser is delivered to saidsecond web browser via said co-browse communication sever over saidco-browse session. 12. The system of Claim 11, wherein said contentprovider is configured to provide an icon for activating saidco-browsing functionality that is overlaid said content at said firstdevice. 13. The system of Claim 12, wherein first device is configuredto determine that said icon is activated, and initiate said co-browsesession through said second communication session to join said first webbrowser into said co-browse session. 14. The system of Claim 11, whereinsaid first device is configured to access a document object model (DOM)of said content, and send said DOM to said co-browse communicationserver for delivery to said second web browser. 15. The system of Claim14, wherein said first device is configure to recognize changes to saidDOM in an updated DOM, and send said updated DOM to said co- browsecommunication server for delivery to said second web browser. 16. Thesystem of Claim 14, wherein said second device is configure to recognizechanges to said DOM in an updated DOM, and send said updated DOM to saidco-browse communication server for delivery to said first web browser.17. The system of Claim 11, wherein said first web browser is configuredto receive a link comprising said co-browse session identifier from saidco-browse communication server and deliver said link to said seconddevice, wherein said link when activated directs a corresponding browserto establish communication with said co- browse communication server tojoin said co-browse session. 18. The system of Claim 17, wherein saidfirst web browser is configured to paste said link into a chat conductedbetween said first device and said second device, or include said linkin an electronic message that is delivered from said first device tosaid second device. 19. The system of Claim 17, wherein said second webbrowser is configured to establish a fourth communication sessionbetween said second web browser and a join page, enter a token into saidjoin page, wherein said token comprises said co-browse sessionidentifier, and direct said second web browser to said co-browsecommunication server to join said second web browser into said co-browsesession based on said token. 20. A method for co-browsing, comprising:establishing a first communication session between a content providerand a first web browser of a first device over a network; deliveringcontent to said first web browser, wherein said content comprisesembedded co-browsing functionality; exposing said co-browsingfunctionality in said content with an icon comprising said co-browsesession identifier, such that when said icon is activated at said firstdevice, said first web browser is joined into said co-browse session asa host, wherein said co- browse session is established between saidfirst web browser and a second web browser of a second device through aco-browse communication server, and wherein said content at said firstweb browser is delivered to said second web browser via said co-browsecommunication server.C2C and B2C Architecture with Multi-Domain Co-Browsing FunctionalityEnabled Through a Web Browser Extension

FIG. 6 is an illustration of an information flow diagram showing theflow of information through a co-browse system 600 that is capable ofestablishing a co-browse session between two or more parties accessingmultiple domains (e.g., web sites) through a co-browsing extension to aweb browser, in accordance with one embodiment of the presentdisclosure. Co-browsing allows participants to simultaneously view thecontent within a co-browse session.

System 600 illustrates a C2C and/or a B2C architecture that provides forco-browsing of online content by at least two participants. Aco-browsing session may be established between a web browser running ona computer associated with the host participant HP 610, and a webbrowser running on a computer system associated with a guest participantGP 620A. Additional guest participants GP 620 B-N may also be includedin the co-browse session. In particular, participant HP 610 acts as ahost in the co-browse session, initiates the co-browse session, andinvites guest participants GP 620 A-N into the co-browse session. Theco-browsing session allows the browsers of participating parties todisplay substantially the same online content (e.g., an html web page),with some modifications for co-browsing depending on whether theparticipant is the host or the guest.

The extension architecture allows for multi-domain co-browsing. That is,because the co-browse functionality is provided as an extension 640 tothe browser at the host participant HP 610, that functionality isimplementable on any content from any content provider. As such, aco-browse session is able to distribute content from any contentprovider. For example, the host participant HP 610 may be viewingcontent from .com server 630 A-N within a browser. That content is alsoavailable to any guest participant GP 620 A-N through the co-browsesession. As shown in FIG. 6, only the device associated with hostparticipant HP-1 has the extension 640 for implementing co-browsing. Inaddition, to distribute the co-browse functionality to each of the guestparticipants GP 620A-N, the co-browsing functionality is added to thecontent and provided to the co-browse communication server 650 and toeach of the guest participants GP 620 A-N through the co-browse session.

A possible use case illustrating the implementation of the C2Carchitecture providing a co-browse session is the shared experience ofonline shopping by two or more participants as previously introduced inthe B2C2C embodiments, except in the C2C architecture multiple .comwebsites may be shared in the co-browse session. In the C2C architectureall the parties may not be connected with or employed by the businessesassociated with the .com servers 630 A-N.

A possible use case illustrating the implementation of the B2Carchitecture providing a co-browse session involves an insurance companyselling insurance to a customer. In the B2C case, the host participantHP 610 may be the agent of the insurance company. A guest participant GP620A is the customer, wherein the agent is helping the customer selectan insurance plan. The co-browse session allows the agent to help thecustomer navigate not only through the insurance company's web site(e.g., showing different insurance plans offered by the insurancecompany), but also allows the agent to show the customer informationfrom other web sites that may be helpful in determining which plan toselect. For instance, the agent may direct the customer in the co-browsesession to a government website “healthcare.gov”. The agent is then ableto help the customer navigate through the healthcare.gov website in theco-browse session to determine what subsidy is available to thecustomer. In the co-browse session, the agent can now direct thecustomer back to the web site hosted by the insurance company todetermine which health plan is best after applying the subsidy. After ahealth plan is selected, the agent is able to help the customer fill inthe proper enrollment forms provided by the insurance company's websitein the co-browse session.

As shown in FIG. 6, a communication session is established between hostparticipant HP 610 and the .com server 630A in step 1, wherein server630A instantiates the .com website and provides content (including code,images, video, or other content related to a web page). Access to thecontent is accomplished through some communication network (not shown),such as, the internet.

At some point, the host participant HP 610 decides to initiate aco-browse session. This may occur before, during, or after connecting toany content provider. For instance, the co-browse session may beestablished and running before the host participant HP 610 has accessedany online content. The co-browsing functionality may be implementedthrough an icon that is displayed by the browser with or withoutcontent. For instance, the start co-browse icon may be implementedthrough a co-browse toolbar or widget that is layered over the content,wherein the icon includes a link. As such, at step 2, after the icon isselected the web browser at the host participant HP 610 is directed tothe co-browse communication server 650 in order to initiate a co-browsesession, and join the browser at host HP 610 into the co-browse session.Once the co-browse session is established, the browser at host HP 610 iscoupled to the communication server 650 through a communication network.

As previously described, the co-browse session is associated with aco-browse session identifier, that is generated by the co-browsecommunication server 650. At step 3, the co-browse communication server650 sends the co-browse session identifier to host HP 610, wherein thesession identifier can be used to join the co-browse session by anypresenter (e.g., guest participants 620 A-N).

At step 4, an invitation to join the co-browse session is delivered toone or more guest participants GP 620 A-N. The invitation and theprocess for inviting the guest is similar to that previously describedin relation to the B2C2C architecture. Specifically, the invitationcontains the co-browse session identifier, or some information that mapsback to the identifier. For example, the invitation may be in the formof an electronic communication (e.g., email, chat, voice, etc.), or maybe in analog form (e.g., voice or note) that contains a token.

For example, the invitation may include a hyperlink (e.g., short URL)that includes the session identifier, wherein the hyperlink directs thecorresponding browser to the co-browse communication server in order tojoin that browser to the co-browse session associated with the co-browsesession identifier. In another example, the invention to join may bepresented with a token. For example, the token may include a passwordwhich when presented to the proper authority (e.g., a join page 670 atstep 5) will direct the corresponding browser to the co-browsecommunication server to join that browser into the co-browse sessionbased on information contained in the token. The token may bedistributed through any means, such as when the host participant phonesthe guest (e.g., associated with GP 620A) and communicates the tokenparticulars (e.g., password). In addition, the host may verbally tellthe guest the network address of the join page. In one implementation,the join page 670 is located at the website supported by .com server630, or is provided by co-browse communication server 650, or may belocated at a separate network location. In still other embodiments, theinvitation to join the co-browse session is made through a messaging orcommunication feature of a social network platform (e.g., co-browsingsocial network, or third party social network [e.g., Facebook, Twitter,Skype, etc.]), wherein both participants are logged into the socialnetwork platform. For example, the hyperlink and/or token along withinvitation details may be presented to a guest by the host through thecommunication channel provided by the social network (e.g., post, mail,chat, messaging, etc.).

The co-browse session is fully established when the guest 620A joins theco-browse session at step 6. As such, the co-browse communication server650 is coupled to the web browser of the host participant 610, and theweb browser of the guest participant 620A through a communicationnetwork (not shown). Additional guests may be added through a similarjoining process. The co-browse communication server 650 acts as aninterface between the web browsers for host HP 610 and guests GP 620A-N, and allows the browsers to display substantially the same onlinecontent (e.g., an html web page). For example, in the co-browse sessionwhatever online content provided to the browser for host HP 610 by .comserver 630 is forwarded to the communication server 650, and thendelivered to the browsers for the guests GP A-N. Further, control (e.g.,cursor click) or navigation information (e.g., cursor position andinteraction) depending on priority and/or rules settings as implementedat host HP 610 is relayed to the communication server 650, and then tothe guests GP A-N.

Further, any interaction by host HP 610 with the online content iscommunicated directly with the .com website (e.g., 630A). Thatinteraction is then updated and delivered back to the browser of the hotHP 610 (e.g., in the form of a new page), updated and/or delivered tothe communication server 650 facilitating the co-browsing, and thenupdated and/or delivered to the browser at guest 620A.

In this manner, each of the guests GP 620A-N is insulated from any ofthe .com servers 630 A-N, and relays all communication to or with .comservers 630 A-N through the communication server 650 and the host HP610. As such, the guests GP 620 A-N are able to interface with theonline content via the host participant HP 610. For example, any actionon the online content by the browser for the guest GP 610A is notdirectly delivered to .com server 630A, and instead is delivered to theco-browse communication server 650, which then delivers the interactioninstruction to the browser at the host HP 610. At that point, thebrowser at host HP 610 will deliver the interaction instruction to the.com server 630A. Further, any control (e.g., cursor click) ornavigation information provided by the guest GP 620A is relayed to thecommunication server 650 and then to the host HP 610 depending onpriority and/or rules settings as implemented at the guest GP 620A.

Because the extension providing co-browsing functionality is on thebrowser of the host participant 610, the .com servers 630 A-N areunaware of the co-browse session between the host 610 and the guests 620A-N. Also, the browsers at the guest participants GP 620 A-N are notrequired to install an extension on their browser, because they receivethe co-browsing functionality through the co-browsing session (e.g.,html, JavaScript, CSS, etc. that is layered on top of the content).

Additionally, the extension allows for multi-domain co-browsing. Inparticular, during the co-browse session content from a second websitemay be accessed. For example, at step 7A, the content from .com server630B is accessed by the browser at host HP 610. That content is thendelivered to the co-browse communication server 650 in step 7B, which isthen delivered to at least one of the guest participants 620 A-N at step7C in the co-browse session. In one implementation, the first browsersession with .com server 630A is still open (e.g., on another tab),while the second browser session with .com server 630B is beingconducted. Additional windows to other content may be implemented. Forexample, at step 8A, the content from .com server 630N is accessed bythe browser at host HP 610. That content is delivered to the co-browsecommunication server 650 at step 8B, which is then delivered to at leastone of the guests 620 A-N at step 8C in the co-browse session.

Again, if the co-browse communication server 650 malfunctions, then thecommunication session between the browser of host HP 610 and the .comserver 650 is unaffected. That is, only the link between the browser atany of the guests GP 620A-N and the communication server 650 will beaffected (e.g., experience lower performance, terminate, etc.).

In another implementation, host HP 610 is an agent of the businessassociated with the .com server 630A. In the example previouslyintroduced, host HP 610 may be associated with an agent of an insurancecompany. Because the host HP 610 associated with the agent acts as thehost in the co-browse session, and is helping the guest participant(e.g., guest 620A) navigate through one or more websites provided by.com servers 630 A-N, one or more rules engines 690 A-N at the guestparticipants GP 620 A-N and rules engine 695 at the host participant 610are implemented to ensure sensitive information provided by the guestsare not accessible by the agent. For example, the agent may help theagent fill out a form available on the insurance company's websiteprovided by .com server 630A. The form may include private information,such as, banking account numbers, or social security numbers. The rulesengines 690 A-N and 695 help to prevent the agent from accessing thatprivate information.

For example, the rules engine 690A at the guest participant 620A is ableto identify sensitive information, and mark that information. Thesensitive information that is marked is then delivered to the co-browsecommunication server, for ultimate delivery back to the .com server630A. this may occur when the guest/customer wants to submit theinformation when enrolling in a healthcare plan. When that sensitiveinformation is passed to the host HP 610 in the co-browse session, therules engine 695 at the host identifies the sensitive informationthrough its markings, and performs additional actions on thatinformation to prevent the agent from accessing (e.g., viewing) thatsensitive information. For instance, the sensitive information may bemasked (e.g., marked with asterisks “*s” in place of text). As such, theunmasked version of the sensitive information can still be deliveredback to the .com server 630A for processing.

FIG. 7 is a flow diagram 700 illustrating steps in a method forestablishing a co-browse session between two or more parties of multipledomains (e.g., web sites) through a co-browsing extension to a webbrowser, in accordance with one embodiment of the present disclosure. Inother embodiments, all or portions of the method outlined in flowdiagram 700 may be implemented as a computer-implemented method; orimplemented as instructions within a computer system including aprocessor and memory configured to execute the instructions; orimplemented as computer/processor executable instructions stored on anon-transitory computer-readable storage medium. Some or all of theoperations performed in diagram 700 are implementable within apparatus100 and/or co-browse system 600 of FIG. 6.

At 710, the method includes establishing a first communication sessionbetween a first web browser of first device (e.g., host participant) anda content provider over a network. The session is established to delivercontent to the first web browser.

At 720, the method includes accessing a co-browse extension on the firstweb browser to enable multi-domain co-browsing functionality. Theco-browsing functionality may be enabled responsive to a request toinitiate co-browsing at the first device. As previously described, theextension allows the host to deliver multi-domain content, from one ormore content providers, to one or more guest participants in a co-browsesession. That is, because the co-browsing functionality is not tied toparticular content from a corresponding content server, and is insteadlocated at the host participant, any content received by the hostparticipant may be distributed through the co-browse session to one ormore guest participants.

For example, the co-browse extension may be accessed through a startco-browsing hyperlink displayable within or overlaid the contentprovided by the browser at the host, that when selected initiates aco-browse session. In particular, after determining that the icon wasactivated making a request to initiate a co-browse session, at 730 themethod includes establishing a second communication session between thefirst web browser and a co-browse communication server to initiate andjoin said first web browser in a co-browse session. The co-browsesession comprises a co-browse session identifier, wherein said firstdevice acts as a host in said co-browse session.

After the co-browse session is established, the co-browse communicationserver delivers the co-browse session identifier to the first device(e.g., host) so that the first device is able to send out invitations toone or more guest participants (e.g., a guess participant at the secondweb server). The session identifier may be included as a link or token,or any other form capable of making an association back to the co-browsesession and the co-browse communication server for joining the co-browsesession. As previously described, the invitation can be in the form of aelectronic communication (e.g., email, chat, voice, etc.) that allowsfor the transfer of the co-browse session identifier, or some otherinformation (e.g., hyperlink) for mapping back to the sessionidentifier. For example, the invitation may be sent via email or withina chat window and include a short hyperlink (e.g., short URL) that whenactivated directs the corresponding browser to the co-browsecommunication server to join that browser into the appropriate co-browsesession using the associated co-browse session identifier. In anotherembodiment, the invitation can be in the form of a token that isdelivered through some secondary communication channel. For example, thetoken may be a password that is communicated through a phone to a guestalong with instructions to enter the token into an addressable join pagein order to join the co-browse session. As such, when the token isauthenticated through the join page, the corresponding browser isdirected to the co-browse communication server through anothercommunication session over the network. In addition, the browser isjoined into the co-browse session based on the session identifier and/orinformation contained in the token.

Once the invitation is accepted, at 740, the method includesestablishing a third communication session between a second web browserof a second device and the co-browse communication server to establishthe co-browse session and join the second web browser into the session.For example, a request to join is delivered to the co-browsecommunication server (e.g., through activation of the co-browsehyperlink), wherein the request includes some reference to the co-browsesession identifier, as previously described. Based on the sessionidentifier, the co-browse communication server is able to identify theproper co-browse session and join the second web browser into theco-browse session.

As a result, the co-browse session between the first web browser as thehost, and the second web browser of the second device as the guest isestablished. In the co-browse session, content at the first web browseris delivered to the second web browser of the second device via theco-browse communication server. In this embodiment, the first deviceacts as the host in the co-browse session, wherein the host maintainsthe original browser session with the content provider to receivecontent, and wherein the host initiates the co-browse session. Forexample, a DOM (e.g., including html, JavaScript, CSS, etc.) of thecontent is accessed at the first web browser and delivered to theco-browse communication server for delivery to the second web browser.The co-browse session allows the two browsers to display substantiallythe same DOM, with some modifications for co-browsing depending oncontrol and priority information as defined for the host or the guest.For instance, changes to the DOM are recognized at one of the webbrowsers of the first and second devices. The changes may include events(e.g., mouse/cursor movement, mouse clicks, etc.). These changes areupdated in the DOM, wherein the updated DOM is delivered to the otherweb server through the co-browse communication server.

Additionally, the host participant may access content from multipledomains of one or more content providers (e.g., .com servers). Becausethe co-browsing extension is located on the host participant, theco-browse session will support the distribution of content from themultiple domains through the co-browse session. For example, whenaccessing additional content, a fourth communication session between thefirst web browser (e.g., host) of the first device and a second contentprovider is established over the network. The second content providerdelivers second content to the first web browser. Further, the secondcontent is delivered from the first web browser to the co-browsecommunication server, which then forwards it to the second web browserof the second device (e.g., at the guest) in the co-browse session. Inone implementation, the first browser session with first contentprovider remains open (e.g., on another tab), while the second browsersession with the second content provider is established and opened.Additional browser sessions with additional content from additionalcontent providers may also be distributed through the co-browse session.

TABLE 3 LISTING OF CLAIMS 1. A method for co-browsing between multipleparties, comprising: establishing a first communication session betweena first web browser of first device and a first content provider over anetwork to deliver content to said first web browser from said firstcontent provider; accessing a co-browse extension on said first webbrowser to enable multi-domain co-browsing functionality on said firstweb browser; establishing a second communication session between saidfirst web browser and a co-browse communication server to initiate andjoin said first web browser in a co- browse session, wherein saidco-browse session comprises a co-browse session identifier, wherein saidfirst device acts as a host in said co-browse session; establishing athird communication session between a second web browser of a seconddevice and said co-browse communication server to join said second webbrowser into said co-browse session, such that content at said first webbrowser is delivered to said second web browser of said second devicevia said co-browse communication server. 2. The method of Claim 1,wherein said accessing a co-browse extension further comprises:responsive to request at said first device, enabling said co-browsingfunctionality at said first device. 3. The method of Claim 2, furthercomprising: determining that a co-browse icon has been activated on saidfirst device. 4. The method of Claim 1, further comprising: receiving alink comprising said co-browse session identifier at said first webbrowser from said co-browse communication server, wherein said link whenactivated directs a corresponding browser to establish communicationwith said co-browse communication server to join said co-browse session.5. The method of claim 4, further comprising: delivering said link tosaid second device. 6. The method of Claim 5, wherein said deliveringsaid link comprises: pasting said link into a chat conducted betweensaid first device and said second device. 7. The method of Claim 5,wherein said delivering said link comprises: including said link in amessage that is delivered from said first device to said second device.8. The method of Claim 4, wherein said establishing a thirdcommunication session comprises: activating said link at said seconddevice. 9. The method of Claim 1, wherein said establishing a thirdcommunication session comprises: establishing a fourth communicationsession between said second web browser and a join page; entering atoken in said join page, wherein said token comprises said co-browsesession identifier; directing said second web browser to said co-browsecommunication server over said third communication session to join saidsecond web browser into said co-browse session based on said token. 10.The method of Claim 1, further comprising: establishing a fourthcommunication session between said first web browser of said firstdevice and a second content provider over said network to deliver secondcontent to said first web browser from said second content provider; anddelivering said second content from said first web browser to saidsecond web browser of said second device via said co-browsecommunication server in said co- browse session. 11. The method of Claim1, further comprising: establishing a first rules engine at said seconddevice to identify sensitive information, and mask said sensitiveinformation; and establishing a second rules engine at said first deviceto identify said sensitive information that is masked. 12. A system forco-browsing between multiple parties, comprising: a first communicationsession established between a first web browser of first device and afirst content provider over a network to deliver content to said firstweb browser from said first content provider; a co-browse extensionaccessible on said first web browser that enables multi- domainco-browsing functionality on said first web browser; a secondcommunication session established between said first web browser and aco-browse communication server to initiate and join said first webbrowser in a co- browse session, wherein said co-browse sessioncomprises a co-browse session identifier, wherein said first device actsas a host in said co-browse session; and a third communication sessionbetween a second web browser of a second device and said co-browsecommunication server to join said second web browser into said co-browse session, such that content at said first web browser is deliveredto said second web browser of said second device via said co-browsecommunication server. 13. The system of Claim 12, further comprising: anicon at said first device that when activated enables said co-browsingfunctionality at said first device. 14. The system of Claim 12, furthercomprising: a link comprising said co-browse session identifierdelivered to said first web browser from said co-browse communicationserver, wherein said link when activated directs a corresponding browserto establish communication with said co-browse communication server tojoin said co-browse session. 15. The system of Claim 12, wherein saidlink is delivered to said second device. 16. The system of Claim 15,further comprising: a chat conducted between said first device and saidsecond device, wherein said link is pasted into said chat. 17. Thesystem of Claim 15, further comprising: a message including said linkthat is delivered from said first device to said second device. 18. Thesystem of Claim 15, further comprising: a fourth communication sessionestablished between said second web browser and a join page; and a tokenentered into said join page, wherein said token comprises said co-browsesession identifier, and wherein said second web browser is directed tosaid co-browse communication server over said third communicationsession to join said second web browser into said co-browse sessionbased on said token. 19. The system of Claim 12, further comprising: afourth communication session established between said first web browserof said first device and a second content provider over said network todeliver second content to said first web browser from said secondcontent provider, wherein said second content is delivered from saidfirst web browser to said second web browser of said second device viasaid co-browse communication server in said co-browse session. 20. Thesystem of Claim 12, further comprising: a first rules engine at saidsecond device to identify sensitive information, and mask said sensitiveinformation; and a second rules engine at said first device to identifysaid sensitive information that is masked.Co-browsing in the Mobile Environment

FIG. 8 is an illustration of the implementation of co-browsing through amobile application 800, in accordance with one embodiment of theinvention. As shown, the mobile application includes co-browsingfunctionality 810, and browser functionality 820 for a mobile device.The mobile application is invoked by a user to access information (e.g.,websites, data, etc.) over a network using the browser functionality. Inaddition, the mobile application is invoked to establish and/orparticipate in a co-browse session. In that manner, a co-browsingsession is established not exactly through a browser or through browserextensions, but through an interaction with a mobile application. Forinstance, the application is manipulating the web page inside thebrowser, or providing co-browsing instructions to the browser. Thisextends the concept of co-browsing to mobile applications.

In one embodiment, the browser functionality is provided through alibrary of functionalities that are selected and used within the mobileapplication 800. For instance, the library may contain one or morebrowser applications suitable for use within the mobile application 800.In that manner, the browser functionality 820 is selectable within thelibrary for use within the mobile application 800.

In one implementation, the browser application may include a nativebrowser application that is provided by the manufacture of the mobiledevice. That is, the co-browsing functionality is paired with the nativebrowsing application.

In another case, the browser application may be a third party (e.g.,enterprise) browser application. For instance, a major retailer may wantto provide co-browsing as a feature for its mobile users. In that case,the major retailer could provide a co-browsing functionality within itsown mobile shopping application. In another case, a corporation (e.g.,an insurance company or banking establishment) may want to include aco-browsing feature within their mobile application, so that an agent ofthe corporation may be able to help a user navigate through the mobileapplication. For example, a user may be using the mobile application ofan insurance company to file a car accident claim. A co-browse sessionmay be established and include an agent of the insurance company and theuser, wherein the agent can help the user fill out an accident claimform provided by the website of the insurance company when making theclaim. As an example of a multiple domain co-browsing session, the agentcan help the user navigate through a mapping domain to find thegeographic location of the accident, and then fill out that informationon the accident claim form.

In still another case, the browser application may be associated withthe co-browsing functionality 810, wherein a user who loads the mobileapplication 800 for purposes of co-browsing, also can automaticallyaccess the corresponding browser feature or functionality 820.Additional features may be provided within the mobile application 800 inthis implementation, such as a chat channel, an offers engine providingoffers to the user, and other functionalities that complement aco-browsing session.

A method for co-browsing in a mobile environment is described, inaccordance with one embodiment of the present disclosure. The methodincludes providing a mobile application executable on a mobile device,wherein the mobile application comprises a co-browsing functionality;and wrapping browser functionality with the mobile application, suchthat web browsing is enabled when executing the co-browsingfunctionality. For example, the browser functionality may be accessedwithin a library of functionalities, such that the method includesproviding a library of functionalities comprising a first functionalityenabling browser functionality; and calling the first functionalitywithin the mobile application. In one embodiment, the mobile applicationcomprises a third party enterprise, such as an insurance company, orretailer, etc.

TABLE 4 LISTING OF CLAIMS 1. A method for co-browsing in a mobileenvironment, comprising: providing a mobile application executable on amobile device, wherein said mobile application comprises a co-browsingfunctionality; and wrapping browser functionality with the mobileapplication, such that web browsing is enabled when executing saidco-browsing functionality. 2. The method of Claim 1, wherein saidwrapping browser functionality with the mobile application comprises:providing a library of functionalities comprising a first functionalityenabling browser functionality; and calling said first functionalitywithin said mobile application. 3. The method of Claim 1, wherein saidmobile application is associated with an third party enterprise.Pointer Differentiation Between Multiple Parties of a Co-Browse Session

FIG. 9 is a diagram illustrating a window 920 of a display of a host ofa co-browsing session, wherein the co-browsing sessions are facilitatedthrough any of the previously described co-browsing methods andarchitectures. For example, in a co-browsing session, the hostestablishes a co-browsing session with a guest. Window 920 is associatedwith the host user, and includes pointer 910 that is controlled by theoperating system of the host device. In one embodiment, the pointer 910of a local device (e.g., in this case the host) is not controlled by theco-browse communication server and does not have any identifyinginformation, and appears without modification on the display of the hostdevice.

On the other hand, as shown in FIG. 9, when in a co-browse session, thepointer 930 for the guest is displayed differently from the pointer 910of the host. For instance, the guest pointer 930 may be larger, or ofdifferent shape, etc. Also, more than one guest pointer may besupported, wherein the co-browse session allows separate and independentcontrol of each of the pointers at the same time. In particular, at eachlocal device, the co-browse functionality (e.g., enabled through browserextension or through code contained within the html content of thedisplayed web page) is configured to query the local browser for pointerposition of the local user. As such, each of the pointers may be movingthroughout the co-browse session at the same time, and theirpresentation on corresponding displays are updated periodically by theco-browse communication server receiving and distributing pointerinformation. On a local display, because each of the pointers isvisually different from other pointers, this allows the participants ofthe co-browse session to more easily track the different pointers fromthe different users.

In addition, with additional identifying information associated with aparticular pointer, the user (e.g., host) is able to immediatelyidentify which participant is controlling a particular pointer within aco-browse session. This is extremely helpful in distinguishing differentpointers when more than two participants are associated with a co-browsesession. For example, the guest pointer 930 may have identificationinformation displayed adjacent to pointer 930. The identifyinginformation may include a name, an avatar, an actual user image, etc.Also, a user identifier may be shown. Other identification informationassociated with the guest may be supported.

Furthermore, other types of information may be displayed in associationwith the guest cursor 930. For instance, the idle time of the pointermay be displayed. In that manner, the user is able to determine whetherthe guest is participating in the co-browse session.

In one embodiment, the position of the guest pointer is updated toreflect movement of the guest pointer, as controlled by the guest on hisor her corresponding display. That is, if the guest moves the guestpointer 930 in relation to online content, that movement andrelationship between the pointer 930 and the online content is alsoreflected in window 920. That is, the movement of the guest pointer 930is updated, so that the host is able to see what actions the guest ismaking. For example, the co-browse functionality of a particular deviceis constantly querying the browser for pointer information (e.g.,location), and delivering that pointer location information to theco-browse communication server which distributes to all the participantsin the co-browse session.

In another implementation, when the guest cursor 930 is inactive for aperiod of time, the cursor is removed from the view of the host. Thatis, it is removed from window 920. The cursor 930 reappears after theguest re-activates the cursor on his or her corresponding display.

In another embodiment, the display for the guest is similarlyconfigured. That is, the cursors are displayed differently for both theguest and the host. Also identification information for the host is nowdisplayed next to the host cursor that is being viewed by the guest.

In one embodiment, a method of displaying multiple pointers in aco-browsing environment is described. The method includes establishing aco-browse session between a host device and one or more guest devices,and displaying a local pointer on the local device. The local pointer iscontrolled by the local operating system. The method includes displayinga remote pointer on the local device (e.g., display), wherein the remotepointer is associated with a device remote from the local device. Forexample, if the local device is associated with a host, then the remotedevice is associated with a guest. Conversely, if the local device isassociated with a guest, then the remote device is associated with thehost or another guest. Also, the remote pointer includes one or morefeatures distinguishing the remote pointer from the local pointer.

In one embodiment, the remote pointer is generated through acommunication server facilitating said co-browse session. That is,information associated with the remote pointer (e.g., pointer location,associated user, avatar, etc.) is gathered by the co-browsecommunication server and then distributed to all participants in theco-browse session.

TABLE 5 LISTING OF CLAIMS 1. A method of displaying multiple pointers ina co-browsing environment, comprising: establishing a co-browse sessionbetween a host device and one or more guest devices; on a local device,displaying a local pointer; and on said local device, displaying aremote pointer, wherein said remote pointer is associated with a deviceremote from said local device, and wherein said remote pointer includesone or more features distinguishing said remote pointer from said localpointer. 2. The method of Claim 1, further comprising: controlling saidlocal pointer by a local operating system. 3. The method of Claim 2,wherein said local pointer is associated with a host. 4. The method ofclaim 2, wherein said local pointer is associated with a guest. 5. Themethod of Claim 1, wherein said local pointer is controlled by a localoperating system. 6. The method of Claim 1, further comprising:generating said remote pointer through a communication serverfacilitating said co-browse session. 7. The method of Claim 1, furthercomprising: providing identifying information adjacent to said remotepointer. 8. The method of Claim 7, wherein said identifying informationcomprises a name. 9. The method of Claim 7, wherein said identifyinginformation comprises an avatar. 10. The method of Claim 1, furthercomprising: tracking location information on a display of said remotepointer; and removing said remote pointer from being displayed on saidlocal device when said remote pointer remains static for a period oftime.Co-Browser Widget

FIG. 10 is an illustration of a window 1000 showing co-browse sessionbetween a host and guest, in accordance with one embodiment of theinvention. The window 100 may be associated with either the host or theguest in the co-browse session. As shown in FIG. 10, a widget or userinterface (UI) 1010 may be displayed in association with the content1020 of the co-browse session in window 1015. In one embodiment, the UI1010 is overlaid the content 1015, or displayed in a manner that iseasily identifiable by the user. In still another embodiment, UI 1010 ismovable within window 1015.

In one embodiment, the UI 1010 identifies the associated participant(e.g., host). For example, a user name 1037 (e.g., host name) may beshown, or other identifying information, such as an avatar or image ofthe user.

Moreover, the UI 1010 provides interfaces that are used to control aco-browsing session. For instance, UI 1010 provides one or more icons orinterfaces that are used to establish settings, provide modes, providegoto links, provide identification, provide identifiers, provide logos,and provide a number of other action items. UI 1010 may be different fordifferent classification of users within a co-browse session. Forinstance, a host UI 1010 may include an invite interface/widget/iconused to invite guests, whereas a guest UI 1010 would not include theinvite interface/widget/icon.

In one case, the UI 1010 includes an interface 1030 that is used toinitiate a co-browse session and invite guests into the co-browsesession by allowing the host to identify the guest. In that case, theinterface 1030 is also used to identify the communication method (email,chat, messaging over a social network platform, etc.) to be used torelay the co-browsing initiation information (e.g., session key) fromthe host to the guest.

In one example, a method is described for inviting a guest into aco-browse session, wherein the guest is logged into a network. Inparticular, on the host side, within the browser, a small extension isinstalled to enable co-browsing via the communication serverfacilitating co-browsing, and invite one or more guests that are loggedinto a network. The log-in may be on any supported and verifiablewebsite, such as, a third party social network, or an insurance companynetwork, or even the website/service that provides co-browsing services.For example, both the host and the guest are logged into the networksupporting the co-browsing, and as such, both are identified to eachother. In the case of a guest that is logged into a third party socialnetworking site, the host is able to select a friend, invite that friendthrough the third party social network communications platform (e.g.,Facebook message on that friend's wall), and establish a co-browsingsession upon acceptance of the invite. More particularly, the extensionprovides for the display of a small co-browsing widget, for example. Inorder to commence co-browsing, the host first logs into the system. Thehost then enters a guest identification field. Since the guest is loggedin, an identification of the guest can be found using the guest's log-ininformation. Once selected, a small message with session number isdisplayed on the guest's computer display (e.g., through a messagingboard) and through the network upon which the guest is logged-in. Whenthe session number is selected, the co-browsing session is established.

In another example, a method for establishing a co-browse session isdescribed, wherein the guest is not logged into any site identifiable bythe co-browse session, in accordance with one embodiment of the presentdisclosure. On the host side, within the browser, a small extension isinstalled to enable co-browsing via the co-browse communication serverfacilitating the co-browsing session, as previously described. Inanother implementation, the functionality is provided at the .comwebsite, as previously described. This extension provides for thedisplay of a small co-browsing widget. In order to commence co-browsing,the user or host first logs into the system. To invite another user tojoin, the host then enters information into a guest identification fieldselectable through interface 1030. The user can enter a guestidentification and a communication method (e.g., email, token, etc.) tothe guest. In one example, the guest is identified via an email address.The email address is used to send the guest an email which contains asession key. Upon the guest selecting the session key, a co-browsingsession is started between the host and guest. The guest need not havethe extension installed on the guest browser. Aside from email, theguest can be contacted via other communication methods, e.g., on-linechat, phone, etc. In addition, no native application need be installedon the guest computer.

In another example, interface 1031 is used to create a snapshot of thecurrent co-browse session for storage into a history of snapshots, aswill be described in relation to FIG. 11. In another example, interface1032 is a “goto” action that is used to specify a new page of a newdomain (e.g., website with new web address) for display in the co-browsesession. In still another example, interface 1035 is used to terminatethe current co-browse session. Still other functionality is supported,such as, a chat function to allow for communication between the host andthe guest.

In one embodiment, the co-browse session is in a guest follows hostmode, as activated by the UI. In this mode, the guest display willfollow the host display. As such, wherever the cursor for the host goesin relation to the online content, the display on the guest will alsoshow that content and the cursor for the host.

In another embodiment, the co-browse session is in a host follows guestmode, as active by the UI. In this mode, the host display will flow theguest display. As such, wherever the cursor for the guest goes inrelation to the online content, the display on the host will also showthat content and the cursor for the guest.

In still another embodiment, another mode allows for independentmovement by each cursor. While the online content (e.g., html web page)is synchronized to both browsers on the host and the guest, the materialon each page need not be synchronized. That is, the web page may belong, wherein a display is only able to show 10-40 percent of the page.In that case, the html code provides all the information to each browserfor the entire page, however, each user may only want to display orinterface with a small percentage of the page. For instance, the hostmay want to interact and display the top 20 percent of the web page. Assuch, the top 20 percent of the web page is displayed and the host'scursor is used to interface with that top 20 percent of the web page. Onthe other hand, the guest may want to interact and display the lower 20percent of the web page. As such, the lower 20 percent of the web pageis displayed and the guest's cursor is used to interface with that lower20 percent. The material for both displays is different, though they aresynchronized to the same web page or content.

TABLE 6 LISTING OF CLAIMS 1. A method of co-browsing, comprising:providing a first user interface viewable on a display of a device; andproviding one or more widgets providing co-browsing functionalities. 2.The method of Claim 1, providing a widget in said user interface on ahost device enabling an initiation of a co-browse session between a hostand at least one guest. 3. The method of Claim 1, further comprising:providing said co-browse session between a host device and one or moreguest devices. 4. The method of Claim 1, further comprising: providingsaid user interface on a host device. 5. The method of Claim 1, furthercomprising: establishing a co-browse session between a host device and aguest device; and providing a second user interface on a guest device,wherein said second user interface comprises one or more widgetsproviding co-browsing functionalities. 6. The method of Claim 5, whereinsaid first user interface comprises a first set of co-browsingfunctionalities, and said second user interface comprises a second setof co-browse functionalities that is different than said first set. 7.The method of Claim 1, further comprising: displaying said userinterface over content of a co-browse session.History Buffer of Screen Shots with Embedded Links

FIG. 11 is an illustration of a history of snapshots 1130 A-N of pagesof one or more websites visited during a particular co-browse session,in accordance with one embodiment of the present disclosure. Inembodiments, the history of snapshots is implemented either in aco-browsing session or in a regular session with one user. For example,during a co-browsing session or regular session, a logged in user cantake a series of screen shots on their visited pages of one or morewebsites. A copy of the page 1130 A-N, in reduced form or full form, isstored in a history buffer. The stored snapshots are available to theuser via an interface or window 1100 that shows the history ofsnapshots. An embedded link to the associated page may also be includedand stored.

For instance, a co-browse session is established between a host and aguest. They visit N number of sites of one or more domains. When on anywebsite, the host and/or guest may decide that they want to save asnapshot of a particular visit to a website. The snapshot functionalitymay be provided through an interface, or widget, or icon on theco-browse widget 1010 of FIG. 10, for example. As such, a snapshot ofthe page (e.g., html, JavaScript, CSS, etc.) is captured at a particularpoint in time. In one embodiment, the host takes the snapshot. Inanother embodiment, the guest may have a control that allows snapshots.In either case, this snapshot is stored in a history of snapshots in arepository associated with the host.

In one embodiment, the stored information may include a link to thecorresponding page that is captured in the snapshot. For example,snapshot 1130-A includes an embedded link. The link will direct thebrowser to the address of the page captured in the snapshot. Theinformation in the current page may be different than the information inthe snapshot, though the address is the same. For example, the page maydisplay an item within a retailer's website. The item may be discountedwith a sale price in the snapshot that is stored, but is now displayedas a full price item in the current page.

In other embodiments, the stored information does not include anembedded link to the corresponding page captured in the snapshot. Forexample, snapshot 1130-B just includes the snapshot of the page, anddoes not include any link.

If a co-browsing session is started or ongoing with the guest, the hostcan select one of these images from the history buffer and the embeddedlink will take the host and the guest to that webpage employing aco-browsing session environment.

In still another embodiment, the screenshots can be annotated withadditional information. For instance, a mark-up of the page is providedvia a pen functionality.

In still another embodiment, a current page of the website isaccessible. By clicking on the link 1120, the host and the guest areable to go to the home page of the web site associated with the onlinecontent contained in the snapshot accessible through link 1120.

TABLE 7 LISTING OF CLAIMS 1. A method of co-browsing, comprising:establishing a co-browse session between a host device and one or moreguest devices; accessing a first page from a first website on saidco-browse session; capturing a first snapshot of said first page; andstoring said first snapshot in a repository associated with a user ofsaid host device. 2. The method of Claim 1, wherein said user is loggedinto a network facilitating said co-browse session. 3. The method ofClaim 1, further comprising: accessing a second snapshot of a secondpage from said first website; and storing said second snapshot in saidrepository. 4. The method of Claim 1, accessing a second snapshot of asecond page from a second website; and storing said second snapshot insaid repository. 5. The method of Claim 1, further comprising: accessingone or more snapshots captured in said co-browse session from saidrepository; and displaying said one or more snapshots in a browsersession.

Thus, according to embodiments of the present disclosure, systems andmethods are described providing for co-browsing.

While the foregoing disclosure sets forth various embodiments usingspecific block diagrams, flowcharts, and examples, each block diagramcomponent, flowchart step, operation, and/or component described and/orillustrated herein may be implemented, individually and/or collectively,using a wide range of hardware, software, or firmware (or anycombination thereof) configurations. In addition, any disclosure ofcomponents contained within other components should be considered asexamples because many other architectures can be implemented to achievethe same functionality.

The process parameters and sequence of steps described and/orillustrated herein are given by way of example only and can be varied asdesired. For example, while the steps illustrated and/or describedherein may be shown or discussed in a particular order, these steps donot necessarily need to be performed in the order illustrated ordiscussed. The various example methods described and/or illustratedherein may also omit one or more of the steps described or illustratedherein or include additional steps in addition to those disclosed.

While various embodiments have been described and/or illustrated hereinin the context of fully functional computing systems, one or more ofthese example embodiments may be distributed as a program product in avariety of forms, regardless of the particular type of computer-readablemedia used to actually carry out the distribution. The embodimentsdisclosed herein may also be implemented using software modules thatperform certain tasks. These software modules may include script, batch,or other executable files that may be stored on a computer-readablestorage medium or in a computing system. These software modules mayconfigure a computing system to perform one or more of the exampleembodiments disclosed herein. One or more of the software modulesdisclosed herein may be implemented in a cloud computing environment.Cloud computing environments may provide various services andapplications via the Internet. These cloud-based services (e.g.,software as a service, platform as a service, infrastructure as aservice, etc.) may be accessible through a Web browser or other remoteinterface. Various functions described herein may be provided through aremote desktop environment or any other cloud-based computingenvironment.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best utilize the invention andvarious embodiments with various modifications as may be suited to theparticular use contemplated.

What is claimed:
 1. A method for co-browsing, comprising: establishing a first communication session between a first web browser of first device and a content provider over a network to deliver content to said first web browser from said content provider, wherein said first device is associated with a first user, wherein said content comprises embedded co-browsing functionality to host a co-browse session; establishing a second communication session between a second device and a co-browse communication server to initiate a co-browse session, wherein said co-browse session comprises a co-browse session identifier, priority information, and rules, wherein said second device acts as a guest in said co-browse session; sending a user identifier associated with said first user and said co-browse session identifier from said second device to said content provider; identifying the first communication session by the content provider based on the previously received user identifier; exposing said co-browsing functionality in said content delivered to said first web browser with an icon comprising said co-browse session identifier, such that when said icon is activated at said first device, said first web browser is joined into said co-browse session; and establishing said co-browse session between said first web browser of said first device as a host and a second web browser of said second device, such that said content at said first web browser is delivered to said second web browser of said second device via said co-browse communication server through said co-browse session by said embedded co-browsing functionality delivered to said first web browser in said content, wherein said second device is insulated from receiving direct communication from said content provider, and wherein said co-browse session allows the host and the guest to display online content from said content provider subject to modifications to a display of said second device for co-browsing depending on said priority information and said rules as defined for the host or the guest.
 2. The method of claim 1, wherein said establishing said co-browse session further comprises: determining that said icon is activated at said first device; establishing a third communication session between said first web browser and said co-browse communication server; delivering said co-browse session identifier from said first web browser to said co-browse communication server in a request to join said co-browse session; and joining said first web browser into said co-browse session based on said co-browse session identifier.
 3. The method of claim 1, wherein said exposing said co-browsing functionality further comprises: identifying said first communication session at said content provider based on said user identifier; accessing said content; and enabling said co-browsing functionality in said content.
 4. The method of claim 3, further comprising: setting a flag that enables said co-browse functionality; generating a new page for said content that is enabled with said co-browse functionality, wherein said new page comprises said icon; and delivering said new page of said content to said first web browser.
 5. The method of claim 1, further comprising: establishing a fourth communication session between said first user and a second user of said second device; and communicating said user identifier of said first user to said second user through said fourth communication session.
 6. The method of claim 5, wherein said fourth communication session comprises voice communication.
 7. The method of claim 1, wherein said establishing a second communication session further comprises: sending said co-browse session identifier from said co-browse communication server to said second web browser.
 8. The method of claim 1, wherein said establishing a first communication session further comprises: authenticating said first user in a log-in process; and associating said first user with said user identifier.
 9. The method of claim 1, further comprising: joining said second web browser into said co-browse session based on said co-browse session identifier.
 10. The method of claim 1, wherein said co-browse functionality in said content provides for: accessing a document object model (DOM) of said content delivered to said first web browser; and sending said DOM to said co-browse communication server for delivery to said second web browser.
 11. The method of claim 10, further comprising: recognizing changes to said DOM in an updated DOM at one of said first and second web browsers; and sending said updated DOM to said co-browse communication server for delivery to the other of said first and second web browsers.
 12. The method of claim 1, further comprising: enabling a rules engine at said first device to filter sensitive information, such that said sensitive information is not delivered to said co-browse communication server.
 13. A system for co-browsing, comprising: a first device comprising a first web browser configured for communicating over a network, wherein said first device is associated with a first user; a content provider providing content comprising embedded co-browsing functionality; a first communication session between said first web browser of said first device and said content provider over said network configured to deliver content to said first web browser from said content provider; a second device comprising a second web browser for communicating over said network; a co-browse communication server (CS) configured to provide a co-browse session comprising a co-browse session identifier, priority information, and rules; a second communication session between said second device and said co-browse communication server to initiate said co-browse session, wherein said second device acts as a guest in said co-browse session, wherein the first communication session is identified by the content provider based on the previously received user identifier; and wherein said co-browse session is established between said first web browser of said first device as a host and a second web browser of said second device through said embedded co-browsing functionality, such that said content at said first web browser is delivered to said second web browser of said second device via said co-browse communication server through said co-browse session by said embedded co-browsing functionality delivered to said first web browser in said content, wherein said second device is insulated from receiving direct communication from said content provider, and wherein said co-browse session allows the host and the guest to display online content from said content provider subject to modifications to a display of said second device for co-browsing depending on said priority information and said rules as defined for the host or the guest.
 14. The system of claim 13, further comprising: a third communication session between said second device and said content provider for delivering said user identifier and said co-browse session identifier to said content provider; wherein said co-browsing functionality in said content delivered to said first web browser is exposed with an icon comprising said co-browse session identifier, such that when said icon is activated at said first device, said first web browser is joined into said co-browse session.
 15. The system of claim 13, wherein said first web browser is configured to deliver said co-browse session identifier to said co-browse communication server in a request to join said co-browse session, and wherein said co-browse communication server is configured to join said first web browser in said co-browse session based on said session identifier.
 16. The system of claim 13, wherein said content provider is configured to identify said first communication session comprising said content based on said user identifier, and to enable said co-browsing functionality in said content.
 17. The system of claim 13, further comprising: a fourth communication session between said first user and a second user of said second device, wherein said fourth communication session is configured for communicating said user identifier to said second user.
 18. The system of claim 13, wherein said co-browse communication server is configured to send said co-browse session identifier to said second web browser for purposes of initiating said co-browse session.
 19. The system of claim 13, further comprising: a rules engine at said first device configured to filter sensitive information, such that said sensitive information is prevented from being delivered to said co-browse communication server.
 20. A method for co-browsing, comprising: establishing a first communication session between a content provider and a first web browser of a first device over a network, wherein said first device is associated with a first user; delivering content to said first web browser, wherein said content comprises embedded co-browsing functionality; receiving a first user identifier, priority information, and rules, associated with said first user and a co-browse session identifier of a co-browse session from a second device, wherein said second device is joined into said co-browse session as a guest; identifying the first communication session by the content provider based on the previously received user identifier; and exposing said co-browsing functionality in said content with an icon comprising said co-browse session identifier, such that when said icon is activated at said first device, said first web browser is joined into said co-browse session as a host, wherein when said co-browse session is established between said first web browser and said second web browser through a co-browse communication server said content at said first web browser is delivered to said second web browser via said co-browse communication server by said embedded co-browsing functionality delivered to said first web browser in said content, wherein said second device is insulated from receiving direct communication from said content provider, and wherein said co-browse session allows the host and the guest to display online content from said content provider subject to modifications to a display of said second device for co-browsing depending on said priority information and said rules as defined for the host or the guest.
 21. The method of claim 20, further comprising: identifying said first communication session based on said user identifier; accessing said content; and enabling said co-browsing functionality in said content. 